Re: JarJar missing...

2005-11-09 Thread Guillaume Laforge
Hello Carlos,

On 08/11/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> Done. All versions however are under the groupId com.tonicsystems

Thanks a lot!

--
Guillaume Laforge
Groovy Project Manager
http://glaforge.free.fr/blog/groovy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



JarJar missing...

2005-11-05 Thread Guillaume Laforge
Hello,

The Groovy project uses jarjar in its M1 build, and we recently
noticed that jarjar-0.5.jar is missing from the ibiblio repository.

There used to be a tonic folder containing the version 0.5.
And now, there's only a jarjar folder containing and old 0.2 version.

Could jarjar-0.5.jar be back in the M1 repository please?

Thanks in advance,

--
Guillaume Laforge
Groovy Project Manager
http://glaforge.free.fr/blog/groovy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [ANN] Maven 2.0 Release Now Available

2005-10-20 Thread Guillaume Laforge
Well done everybody for this great achievement!
I'm looking forward to have (more) fun with Maven 2.0 :-)

Guillaume

On 20/10/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> We are pleased to announce that Maven 2.0 has been released, and is
> available for download from http://maven.apache.org/maven2/download.html
>
> Maven is a build system that provides software project management and
> dependancy comprehension. Based on the concept of a project object model
> (POM), Maven manages a project's build, reporting and documentation from
> a central place.
>
> Maven 2.0 is a rewrite of the popular Maven application, designed to
> both address previous functional requirements and provide a stable
> platform for extending and enhancing its build management framework.
>
> This release is significantly faster and smaller than Maven 1.0 and
> includes the following usability and performance improvements:
>
> * Enhanced Dependency Management - includes dependency closures
>(transitive dependencies), version ranges, automatic build
>numbering, and automatic updating on a configurable interval
>
> * Defined Build Lifecycle - developers can build any type of project
>using standard commands such as compile, test and install
>
> * Unified Project Definition - manages all required build information in
>a single POM now, including project information, dependencies and
>plugin configuration
>
> * Extended Plugin Architecture - supports Java and scripting languages
>such as Beanshell for plugin development
>
> * Better Repository Support - includes separated snapshot repositories,
>a new more managable layout and per-project definitions of new
>repositories
>
> * Expanded Reactor Operation - offers built-in support for multiple
>projects (without the need to perform a full install cycle to compile
>all projects) and support for project aggregation
>
> * New Site Management Tools - supports multiple input and output
>formats, with input formats including wiki-like APT format and
>docbook, while continuing to support traditional Maven XDoc and FAQ
>format.
>
> * New Reporting API - offers a standardised method for producing project
>information and reports
>
> * And much more...
>
> The Maven 2.0 release is considered stable and includes a Maven 1.0
> complete feature set, with additional functionality. The most popular
> Maven 1.0 plugins have been converted for Maven 2.0, and many more are
> available in beta.
> See http://docs.codehaus.org/pages/MAVEN/Maven+Plugin+Matrix for more
> information on particular plugins.
>
> Maven's advanced dependency management features rely on project
> metadata. If you are interested in improving support for the users of
> your project, see http://maven.apache.org/maven2/project-faq.html
>
> The Maven team would like to express thanks to the user and developer
> community for their beta testing, feedback and contributions that helped
> make the release possible!
>
> To get started with Maven now, see the getting started guide:
> http://maven.apache.org/maven2/guides/getting-started/index.html
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Guillaume Laforge
http://glaforge.free.fr/blog/groovy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Task list of "// TODO" comments

2005-05-27 Thread Guillaume Laforge
> I wanted to know if someone has already written a task list plugin that
> work for "// TODO" comments, as Eclipse uses this kind of task tag in the
> Java code.

And of course, we could parametrize some variable to specify different
regex for the TODO pattern to match. That'd be great!

-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Professional Java Tools for Extreme Programming

2005-05-12 Thread Guillaume Laforge
On 12/05/05, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> If you could wait for some weeks, here is the new Vincent Massol's book:
> http://www.oreilly.com/catalog/mavenadn/index.html
> (available mid-June)

I reviewed Vincent's book, and I can tell you it's worth the wait ;-)

-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tag and Groovy

2005-05-01 Thread Guillaume Laforge
Hello Sean,

I'm back with some good news for you.

On 25/04/05, M. Sean Gilligan <[EMAIL PROTECTED]> wrote:
> [...]
> Using ant 1.6.1, I can use the ant 

Re: tag and Groovy

2005-04-26 Thread Guillaume Laforge
Hello Sean,

On 25/04/05, M. Sean Gilligan <[EMAIL PROTECTED]> wrote:
> [snip]
> My first choice would be Groovy (or perhaps Beanshell) as I don't want to 
> learn Python, and am not sure JavaScript gives me the file access that I 
> need.  (I know Groovy has its warts, but it works fairly well for me in short 
> scripts.)
> [snip]

I managed to use Groovy scripts inside Maven with the Groovy Ant task
which will be shipping in the next version of Groovy (it's currently
in CVS head only).

So if you want to use some Groovy code in your build, you'll have to
build Groovy from sources, or wait for a few weeks the next release
(jsr-02).

I've had hard times trying to find a solution to acces the POM and
other objects, but I've managed to find a very ugly workaround to make
that possible:


 
  


def contextField = 
project.propsHandler.class.getDeclaredField("context")
contextField.setAccessible(true)
def context = contextField.get(project.propsHandler)
println context.project.class

  


Unfortunately, the GrantProject instance (here the variable project)
has got a context which is private, and that I could only access
through the setAccessible(true) magic. What a pain...
I wonder why there's no getter on the context! That would be so much better!

In my project.xml, I've added the dependency on groovy-all-.jar
which I've added manually to my local repository (since the next
version of Groovy is not yet out in the wild) :


  groovy
  groovy-all
  1.0-jsr-02-SNAPSHOT
  
root
  


And after that... that works.

We could probably write a small Groovy Maven plugin for that, to
simplify the dirty stuffs.

Question to Maven developers:

Why can't we access the context within the propsHandler of
GrantProject? That would simplify the job :-)

-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Using Maven's Castor Plugin

2005-04-26 Thread Guillaume Laforge
You'll have to specify the castor namespace:



And add some dependencies as well, such as castor, xerces, and a few
commons-xxx. I don't know them by heart.

Guillaume

On 26/04/05, Dinesh Pandey <[EMAIL PROTECTED]> wrote:
> Hi Guillaume,
> 
> I tried the exact same thing but I get the following error:
> 
> 
> 
> __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
> 
> Fatal Error [line 3, row 87]: The prefix "castor" for element
> "castor:generate"
> is not bound.


-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Using Maven's Castor Plugin

2005-04-26 Thread Guillaume Laforge
Hello Dinesh,

You'll have to:

- create a maven.xml (if you don't have already one).

- define a new goal a bit like that:

  


  

- call that goal before java:compile with:

  

  

- you may have to use the castorbuilder.properties file to make some
namespace/package mappins if you don't use the package attribute
(especially if you have some more complex multi-file xsd system)

And you should be done!

Guillaume

On 26/04/05, Dinesh Pandey <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I am trying to use the Maven's castor plugin for source code generation
> based on xsd file.
> 
> When I see the documentation it talks about only one goal
> castor:prepare-filesystem.
> 
> It also talks about a tag called castor:generate but its not clear how do I
> use this tag into my project.
> 
> Could someone please help me with this?
> 
> Thanks in advance,
> 
> Dinesh
> 
> 


-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Deprecated maven.src.dir and references

2005-04-15 Thread Guillaume Laforge
On 15/04/05, Sebastien Arbogast <[EMAIL PROTECTED]> wrote:
> I'm a maven newbie and I have a little problem with property
> definitions. In maven documentation, it's said that the property
> maven.src.dir is deprecated and should be replaced by the 
> element of the pom.
> But I used maven.src.dir in project.properties to define other path
> properties that depend on maven.src.dir.
> So my question is : if I only use  element in POM to define
> my source dir, how can I refer to this definition in
> project.properties and other elements of project.xml and maven.xml ?
> I guess there is a way to do so with some jelly syntax but I don't
> know jelly that much...

If I'm not mistaken: ${pom.build.sourceDirectory} should do.

-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Proxy settings and different remote repos

2005-04-11 Thread Guillaume Laforge
Hello,

I want to use two different repositories: a company-wide repository,
and in second place to fall through to ibiblio if I can't find an
artifact in the company repository.

The problem comes in when I have to specify my proxy settings: to
access my company repo, I don't need to specify my proxy settings, but
to access ibiblio, that's mandatory.

So the question is: is there a solution to that dilema? How can I
specify two remote repositories requiring different proxy settings (or
no settings at all to be clear)? Does Maven provide some magic
parameters for that?

Thanks in advance,

-- 
Guillaume Laforge
http://glaforge.free.fr/weblog/?catid=2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]