Re: Better way to capture output from a Maven job

[stug23]

I also noted that someone has requested that help:evaluate values be returned
in quiet mode:

https://github.com/apache/maven-plugins/pull/17



--
View this message in context: 
http://maven.40175.n5.nabble.com/Better-way-to-capture-output-from-a-Maven-job-tp5790942p5790951.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Better way to capture output from a Maven job

[stug23]

I have a script that needs to obtain the three-part numerical version from a
Maven pom.xml. I am using the Maven help plugin to the version number as
follows:

mvn help:evaluate -Dexpression=project.version

Of course when running the Maven job, you get a great deal of output lines
and towards the end the project.version number. In my script I use a grep to
snatch the three-part numerical version from the Maven output:

mvn help:evaluate -Dexpression=project.version | grep -o
'^[0-9]*\.[0-9]*\.[0-9]*'

So if I have a pom.xml with project/version = 1.2.3-SNAPSHOT, the command
above returns the result '1.2.3'

While this works okay, I would have hoped for a better way to return a value
from Maven. Is there a return/result parameter of some sort such that I
don't have to pick the result out of the entire text output of the Maven job
execution?



--
View this message in context: 
http://maven.40175.n5.nabble.com/Better-way-to-capture-output-from-a-Maven-job-tp5790942.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Warning when using expression for version in pom.xml

[stug23]

I got at least one feedback on this question over in the Google Group for
Continuous Delivery:

https://groups.google.com/d/msg/continuousdelivery/hdlALMDuiyU/jLMBYTbJ0MEJ

Anyone here have opinions or experience with this question?

Thanks.

--
View this message in context: 
http://maven.40175.n5.nabble.com/Warning-when-using-expression-for-version-in-pom-xml-tp5134463p5140277.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Warning when using expression for version in pom.xml

[stug23]

I am investigating the use of an expression for the value of the version in
the  pom.xml. There are properties that fully specify the actual value of
the version in the same pom.xml, so I'm not sure why the warning is issued.
The expression is correctly evaluated (i.e., value = 1.2.0-67936). The
purpose of the expression is to help support continuous delivery - see the
following link for more details on this approach:

https://groups.google.com/d/msg/continuousdelivery/hdlALMDuiyU/brtjqCqyFd4J

So my question is: "Will this warning turn into a fatal build error in the
future?"

*warning message
*
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for com.foo.library:continuous-delivery:jar:1.2.0-67936
[WARNING] 'version' contains an expression but should be a constant. @
com.foo.library:continuous-delivery:${main.version}-${build.number},
/export/home/patp/CONTINUOUS_DELIVERY/VERSION/continuous-delivery/pom.xml,
line 13, column 11
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.

*relevant bits from pom.xml*

/Note that SNAP is default value for svn.revision; alternate value comes
from svn revision number as -Dsvn.revision=67936 in the example:/

com.foo.library
continuous-delivery
${main.version}-${build.number}
. . .

SNAP
${svn.revision}
1.2.0


--
View this message in context: 
http://maven.40175.n5.nabble.com/Warning-when-using-expression-for-version-in-pom-xml-tp5134463p5134463.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

jmockit in Maven Central

[stug23]

I spotted this post over in the jmockit issues page:

http://code.google.com/p/jmockit/issues/detail?id=172

They seem to feel it's too hard to get artifacts into Maven Central. 

Can anyone here comment on this?

Thanks

--
View this message in context: 
http://maven.40175.n5.nabble.com/jmockit-in-Maven-Central-tp4550193p4550193.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: RE: Continuous Delivery and Maven

[stug23]

Stephen's solution makes sense to me. It doesn't try to conflate the meaning
of SNAPSHOTs and it retains the metadata in trunk that keeps everything in
the Maven build instead of relying on an outside tool.

Anyone see any issues with this approach? I think I like it from what I
understand so far.

Thanks!

-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3257778.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Continuous Delivery and Maven

[stug23]

We need to figure out how to best leverage Maven (keeping in mind its process
and practices) in a Continuous Delivery solution. I like the conversation
around this topic and also see that there is this other discussion about the
meaning of CD versus CI.

>From the comments so far, there has been a fair amount of discussion about
how to use SNAPSHOTs as if they were something that they aren't. Namely
retaining SNAPSHOTs all the way through release, possibly mutating the
metadata to make the builds products look like released artifacts instead of
SNAPSHOTs without having to rebuild the binaries. Since a SNAPSHOT works
well for a "work in progress" and not for a "thing I want to keep", maybe a
different approach would work better.

Maybe it would make more sense to just burn lots of version numbers (e.g,
3.5.1099) and always release with a new yet-to-be-defined Maven release
plugin that reflects the processes involved with CD. If the concern is disk
usage or inefficiency, perhaps some automation can make this more
manageable?

I would be interested in inputs on this topic from the Maven founders if
they are following this thread.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3255592.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Continuous Delivery and Maven

[stug23]

I suspect that there is a reasonable way to adjust the builds in Maven such
that they robustly support Continuous Delivery. I know that Jason van Zyl
has started looking at CD as well.

On the Google forum

Chris Hilton commented:

3. In my ideal world, I would probably either extend the release
plugin or write a new one with functionality to take a snapshot
artifact and make it a release artifact, which would still introduce
slight changes but pretty mild ones. I thought I had read a feature
request or wish list about this, but can't find it now. 

The current Maven release plugin, as it is, was not designed to handle the
notion of CD. So it does make sense to tailor this aspect of releasing Maven
artifacts to better support CD.

Also a quick examination of the Maven versions plugin shows that it has
facilities to handle updating versions of projects and their dependencies.
So it looks as if it is more a matter of adjustment of Maven build to
produce a result that aligns with CD than a matter of Maven not being
suitable for CD. I think that the main stumbling block is SNAPSHOTS because
they inherently are not releasable -- part of the process of releasing with
the current Maven release plugin is to fail when there are SNAPSHOT
dependencies.

Another clear requirement for any changes to Maven or its build behavior is
that the current behavior must be maintained for the many projects that
haven't embraced (or won't embrace) Continuous Delivery. So I imagine a
Maven build's behavior being altered through configuration (or a switch of
some sort) to comply with the desired behavior inherent in Continuous
Delivery with respect to the release of artifacts. The major difference
would appear to be with the SNAPSHOT dependencies and the Maven release
process. Other aspects of Maven are for the most part already good as they
are for CD.

This is an interesting challenge that I am sure is best served by a thorough
examination by the Maven and CD experts out there.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3254121.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Continuous Delivery and Maven

[stug23]

I wanted to comment on something we have done for our builds with respect to
SNAPSHOTS that helps with being able repeat a build for the SNAPSHOT. We
record the Subversion revision number for each SNAPSHOT in the MANIFEST.

Also we have a so-called base-pom, which all projects inherit from, that
locks down all of the Maven plugin versions so that the build is repeatable
at a later time.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3254127.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Continuous Delivery and Maven

[stug23]

I've been reading about Continuous Delivery 
and trying to understand how to best combine Maven and Continuous Delivery.
There is a thread in the Continuous Delivery google group where this
discussion has started:



I would be curious as to whether there are other Maven developers following
the Maven Users forum that have been looking Continuous Delivery and trying
to grapple with the best way to use Maven in this approach.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3245370.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Way to customize file names in archetypes?

[stug23]

In your archetype, you can use variable substitutions wherein a variable name
is enclosed with two underscores before and after the property name. These
variable substitutions are intended to take place during project creation.

For example, shown below is a directory name within the archetype resources
that has been expressed using the property 'rootArtifactId'. So if
rootArtifactId=purchase-order, then the final, interpolated name of the
directory in the new project instance will be purchase-order-service.

__rootArtifactId__-service

The same sort of substitution can be used for filenames as well as for
directory names. While 'rootArtifactId' is a standard property in the
archetype, you can also supply your own properties and use them in this same
manner.


Kent Narling wrote:
> 
> Is there any way to customize the names of the files generated by an
> archetype?
> 
> eg I would like to generate a shell file that is installed by the
> project and naturally this shell file should be named according to one
> of the archetype properties...
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Way-to-customize-file-names-in-archetypes--tp27721206p27729518.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How do I find the Jar that conatains this method signature?

[stug23]

You can easily research the class by using the very handy jarvana.com web
site:

  


>From the search link above you can drill into the class to see all of the
methods.

For example:

   



laredotornado wrote:
> 
> Hi,
> 
> I'm using an older version of Maven (1.1) for my project.  I am getting
> the error when running unit tests ...
> 
> org.apache.xpath.compiler.FunctionTable.installFunction(Ljava/lang/String;Ljava/lang/Class;)I
> java.lang.NoSuchMethodError:
> org.apache.xpath.compiler.FunctionTable.installFunction(Ljava/lang/String;Ljava/lang/Class;)I
> at
> com.gargoylesoftware.htmlunit.html.xpath.XPathAdapter.initFunctionTable(XPathAdapter.java:52)
> at
> com.gargoylesoftware.htmlunit.html.xpath.XPathAdapter.(XPathAdapter.java:68)
> at
> com.gargoylesoftware.htmlunit.html.xpath.XPathUtils.evaluateXPath(XPathUtils.java:128)
> at
> com.gargoylesoftware.htmlunit.html.xpath.XPathUtils.getByXPath(XPathUtils.java:72)
> at
> com.gargoylesoftware.htmlunit.javascript.host.HTMLCollection.computeElements(HTMLCollection.java:245)
> 
> 
> Does anyone know how I can figure out what JAR and its specific version
> contains the class and method with the specified signature?  I want to use
> htmlunit 2.5 and as such, thought I had included all the relevant JARs in
> my dependency list, but I guess not.  
> 
> Project.xml is below.  Thanks, - Dave
> 
> 
> Begin project.xml ==
> 
> 
>   ../project.xml
>   myco-dor-online-interlock-test
>   myco-dor-online-interlock-test
>   myco Interlock Tests
>   myco Interlock Tests
>   
>   
>   src/main/test
>   
>   
>   **/*Test.java
>   
>   
>   
>   
>   
> ${basedir}/src/main/resources
>   
>   **/*.xml
>   **/*.properties
>   
>   
>   
>   
> ${basedir}/../service/src/main/resources
>   
>   **/*.xml
>   
>   
>   
>   
>   
>   
>   myco.dor.online.interlock
>   myco-dor-online-interlock-model
>   ${pom.currentVersion}
>   
>   true
>   true
>   
>   
>   
>   myco.dor.online.interlock
>   
> myco-dor-online-interlock-service
>   ${pom.currentVersion}
>   jar
>   
> 
>   
>   net.sourceforge.jwebunit
>   jwebunit-htmlunit-plugin
>   2.2
>   
>   
>   junit
>   junit
>   3.8.1
>   
>   
>   net.sourceforge.cssparser
>   cssparser
>   0.9.5
>   
>   
>   net.sourceforge.htmlunit
>   htmlunit
>   2.5
>   
>   
>   net.sourceforge.htmlunit
>   htmlunit-core-js
>   2.5
>   
>   
>   net.sourceforge.jwebunit
>   jwebunit-commons-tests
>   2.2
>   
>   
>   net.sourceforge.jwebunit
>   jwebunit-core
>   2.2
>   
>   
>   net.sourceforge.nekohtml
>   nekohtml
>   1.9.12
>   
>   
>   org.mockito
>   mockito-all
>   1.7
>   
>   
>   org.mortbay.jetty
>   jetty
>   6.1.12
>   
>   
>   
>   org.slf4j
>   slf4j-api
>   1.5.0
>   
>   
>   org.slf4j
>   slf4j-log4j12
>   1.5.0
>   
>   
>   org.w3c.css
>   s

Basic question on dependency:unpack plugin goal - use of destFileName?

[stug23]

Examples for using dependency:unpack show a configuration property:

   [ filename ]


however I can't get this to work. In other words unpack a file from a zip
and rename it in its destination.

Is this simply in the unpack goal because the artifactItem includes
destFileName, but it doesn't apply for an unpack?

TIA!

-- 
View this message in context: 
http://old.nabble.com/Basic-question-on-dependency%3Aunpack-plugin-goal---use-of-destFileName--tp26822715p26822715.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: xmltask-equivalant Maven plugin

[stug23]

There is a Maven XML plugin that uses XSLT to transform a document that you
may want to have a look at:

   



lukewpatterson wrote:
> 
> Does anyone know of a Maven plugin which provides functionality similar to
> the "xmltask" [1] Ant Task?
> 
> description:
> "
> Uses include:
> * modifying configuration files for applications during builds
> ...
> "
> 
> usage example:
> ---
> original file, src/blah.xml:
>   
> 
>   
> inserting the "name"
>
>  
>   
> which results in:
>   
> Tiger
>   
> ---
> 
> If there isn't a direct Maven plugin, I'll try wrapping in a
> maven-antrun-plugin call.  The only problem then is that xmltask isn't in
> central.  I logged an enhancement request [2] for that issue.
> 
> 
> Thanks,
> 
> Luke
> 
> [1] http://www.oopsconsultancy.com/software/xmltask/
> [2]
> http://sourceforge.net/tracker/?func=detail&aid=2914839&group_id=27398&atid=390338
> 

-- 
View this message in context: 
http://old.nabble.com/xmltask-equivalant-Maven-plugin-tp26803518p26806518.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How can I drop a custom Velocity tool into archetype:generate?

[stug23]

Unfortunately I never did find a way to do what I described in the posting.

Perhaps this could eventually be a feature in Maven 3?


matinh wrote:
> 
> Hi stug23!
> 
> Did you make any progress on this topic? If yes, could you please explain
> the details.
> 
> tia,
> - martin
> 
> On 07 Sep 2009, stug23 wrote:
> 
>> 
>> Can anyone give pointers for this question?
>> 
>> 
>> stug23 wrote:
>> > 
>> > Is there some way to use Plexus injection to accomplish the addition of
>> a
>> > custom Velocity tool in an archetype so that archetype:generate can
>> > leverage the custom Velocity tool?
>> > 
>> > I recently read an introductory posting on Plexus injection on the
>> > Sonatype blog, however I don't know whether it's possible to use Plexus
>> > for the case described above?
>> > 
>> > Sonatype blog article on Plexus injection:
>> > 
>> > Plexus Container Five Minute Tutorial
>> > 
>> >   
>> >
>> <http://www.sonatype.com/people/2009/05/plexus-container-five-minute-tutorial/>
>> > 
>> > 
>> > stug23 wrote:
>> >> 
>> >> I am finishing up a multimodule project archetype which needs to do
>> some
>> >> minor string transformations based on the standard archetype property
>> >> 'rootArtifactId'.
>> >> 
>> >> For example, if rootArtifactId = "purchase-order"  the requirement is
>> to
>> >> produce a derived string assigned using a Velocity directive. One
>> example
>> >> of this might be something like:
>> >> 
>> >> #set( $camelCase = $myCustomTool.capitalize(${rootArtifactId})  )
>> >> 
>> >>which yields $camelCase = "PurchaseOrder" from $rootArtifactId =
>> >> "purchase-order"
>> >> 
>> >> I already have the custom Velocity tool written and working correctly
>> as
>> >> a standalone Java program, however I haven't found any specific
>> >> information on how to incorporate this custom Velocity tool in an
>> >> archetype.
>> >> 
>> >> So my question is: "Is it possible to configure a custom Velocity tool
>> in
>> >> a VelocityContext and have it available to use during the Velocity
>> >> processing part of project instantiation that occurs for
>> >> archetype:generate in an archetype?"
>> >> 
>> >> If the answer is yes, are there any examples of how to do this?
>> >> 
>> >> I searched far and wide in the forums where I did see some indications
>> >> that this idea was at least discussed, if not implemented. For example
>> in
>> >> the following Nabble posting,
>> >> 
>> >>
>> <http://www.nabble.com/-m2--Archetype-Plugin-parameters-and-templates-to966996.html#a977701>
>> >> 
>> >> Jason van Zyl said:
>> >> 
>> >> "The templates are velocity templates so you get the directives that
>> >> velocity provides and you can make your own velocity macros or tools.
>> A
>> >> tool is simply a Java object that you drop into a velocity context so
>> you
>> >> can really do whatever you want. I would think velocity itself would
>> give
>> >> you enough flexibility. "
>> >> 
>> >> TIA!
>> >> 
>> >> 
>> >> 
>> >> 
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/How-can-I-drop-a-custom-Velocity-tool-into-archetype%3Agenerate--tp25207677p25337553.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
> 
> 
>  
> 

-- 
View this message in context: 
http://old.nabble.com/How-can-I-drop-a-custom-Velocity-tool-into-archetype%3Agenerate--tp25207677p26203835.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How can I drop a custom Velocity tool into archetype:generate?

[stug23]

Can anyone give pointers for this question?


stug23 wrote:
> 
> Is there some way to use Plexus injection to accomplish the addition of a
> custom Velocity tool in an archetype so that archetype:generate can
> leverage the custom Velocity tool?
> 
> I recently read an introductory posting on Plexus injection on the
> Sonatype blog, however I don't know whether it's possible to use Plexus
> for the case described above?
> 
> Sonatype blog article on Plexus injection:
> 
> Plexus Container Five Minute Tutorial
> 
>   
> <http://www.sonatype.com/people/2009/05/plexus-container-five-minute-tutorial/>
> 
> 
> stug23 wrote:
>> 
>> I am finishing up a multimodule project archetype which needs to do some
>> minor string transformations based on the standard archetype property
>> 'rootArtifactId'.
>> 
>> For example, if rootArtifactId = "purchase-order"  the requirement is to
>> produce a derived string assigned using a Velocity directive. One example
>> of this might be something like:
>> 
>> #set( $camelCase = $myCustomTool.capitalize(${rootArtifactId})  )
>> 
>>which yields $camelCase = "PurchaseOrder" from $rootArtifactId =
>> "purchase-order"
>> 
>> I already have the custom Velocity tool written and working correctly as
>> a standalone Java program, however I haven't found any specific
>> information on how to incorporate this custom Velocity tool in an
>> archetype.
>> 
>> So my question is: "Is it possible to configure a custom Velocity tool in
>> a VelocityContext and have it available to use during the Velocity
>> processing part of project instantiation that occurs for
>> archetype:generate in an archetype?"
>> 
>> If the answer is yes, are there any examples of how to do this?
>> 
>> I searched far and wide in the forums where I did see some indications
>> that this idea was at least discussed, if not implemented. For example in
>> the following Nabble posting,
>> 
>> <http://www.nabble.com/-m2--Archetype-Plugin-parameters-and-templates-to966996.html#a977701>
>> 
>> Jason van Zyl said:
>> 
>> "The templates are velocity templates so you get the directives that
>> velocity provides and you can make your own velocity macros or tools. A
>> tool is simply a Java object that you drop into a velocity context so you
>> can really do whatever you want. I would think velocity itself would give
>> you enough flexibility. "
>> 
>> TIA!
>> 
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-drop-a-custom-Velocity-tool-into-archetype%3Agenerate--tp25207677p25337553.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How can I drop a custom Velocity tool into archetype:generate?

[stug23]

Is there some way to use Plexus injection to accomplish the addition of a
custom Velocity tool in an archetype so that archetype:generate can leverage
the custom Velocity tool?

I recently read an introductory posting on Plexus injection on the Sonatype
blog, however I don't know whether it's possible to use Plexus for the case
described above?

Sonatype blog article on Plexus injection:

Plexus Container Five Minute Tutorial

  
<http://www.sonatype.com/people/2009/05/plexus-container-five-minute-tutorial/>


stug23 wrote:
> 
> I am finishing up a multimodule project archetype which needs to do some
> minor string transformations based on the standard archetype property
> 'rootArtifactId'.
> 
> For example, if rootArtifactId = "purchase-order"  the requirement is to
> produce a derived string assigned using a Velocity directive. One example
> of this might be something like:
> 
> #set( $camelCase = $myCustomTool.capitalize(${rootArtifactId})  )
> 
>which yields $camelCase = "PurchaseOrder" from $rootArtifactId =
> "purchase-order"
> 
> I already have the custom Velocity tool written and working correctly as a
> standalone Java program, however I haven't found any specific information
> on how to incorporate this custom Velocity tool in an archetype.
> 
> So my question is: "Is it possible to configure a custom Velocity tool in
> a VelocityContext and have it available to use during the Velocity
> processing part of project instantiation that occurs for
> archetype:generate in an archetype?"
> 
> If the answer is yes, are there any examples of how to do this?
> 
> I searched far and wide in the forums where I did see some indications
> that this idea was at least discussed, if not implemented. For example in
> the following Nabble posting,
> 
> <http://www.nabble.com/-m2--Archetype-Plugin-parameters-and-templates-to966996.html#a977701>
> 
> Jason van Zyl said:
> 
> "The templates are velocity templates so you get the directives that
> velocity provides and you can make your own velocity macros or tools. A
> tool is simply a Java object that you drop into a velocity context so you
> can really do whatever you want. I would think velocity itself would give
> you enough flexibility. "
> 
> TIA!
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-drop-a-custom-Velocity-tool-into-archetype%3Agenerate--tp25207677p25226450.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multiple executions of goals under generate-sources: How to avoid?

[stug23]

The approach that I used could be applied for any mojo.

Below is an outline of the basic code I used in the mojo execute() method.

I simply create a new property (generation.finished) that I can check for on
subsequent executions of the mojo:

--
Object generationFinished =
this.mavenProject.getProperties().get("generation.finished");
boolean generationIsFinished = (generationFinished == null) ? false: true;
if (generationIsFinished) {
   getLog().info("skipping code generation ... source code is up to date");
} else {
   getLog().info("Starting code generation ...");
   ...
   ..
   .
   // mark the code generation as complete:
   this.mavenProject.getProperties().put("generation.finished", "true");
}
--


ZsJoska wrote:
> 
> Do you have a sample for doing that? It's your solution generic?
> I have a web services client application where I generate the artifact
> sources during the generate-sources phase. In order to import the latest
> version of the wsdl I try to kick-up a jetty server with the war produced
> by another module.
> The second execution of the jetty stops the build with error Address
> already in use.
> 
> Thanks,
> Jozsef
> 
> 
> stug23 wrote:
>> 
>> Lacking any other solution I went ahead and incorporated an internal
>> Maven property that gets set at the end of the first code generation in
>> the lifecycle. That way subsequent checks of the property provide an
>> indication to skip code generation.
>> 
>> This seems kind of kludgy but it works 
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multiple-executions-of-goals-under-generate-sources%3A-How-to-avoid--tp20038097p25207750.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

How can I drop a custom Velocity tool into archetype:generate?

[stug23]

I am finishing up a multimodule project archetype which needs to do some
minor string transformations based on the standard archetype property
'rootArtifactId'.

For example, if rootArtifactId = "purchase-order"  the requirement is to
produce a derived string assigned using a Velocity directive. One example of
this might be something like:

#set( $camelCase = $myCustomTool.capitalize(${rootArtifactId})  )

   which yields $camelCase = "PurchaseOrder" from $rootArtifactId =
"purchase-order"

I already have the custom Velocity tool written and working correctly as a
standalone Java program, however I haven't found any specific information on
how to incorporate this custom Velocity tool in an archetype.

So my question is: "Is it possible to configure a custom Velocity tool in a
VelocityContext and have it available to use during the Velocity processing
part of project instantiation that occurs for archetype:generate in an
archetype?"

If the answer is yes, are there any examples of how to do this?

I searched far and wide in the forums where I did see some indications that
this idea was at least discussed, if not implemented. For example in the
following Nabble posting,



Jason van Zyl said:

"The templates are velocity templates so you get the directives that
velocity provides and you can make your own velocity macros or tools. A tool
is simply a Java object that you drop into a velocity context so you can
really do whatever you want. I would think velocity itself would give you
enough flexibility. "

TIA!



-- 
View this message in context: 
http://www.nabble.com/How-can-I-drop-a-custom-Velocity-tool-into-archetype%3Agenerate--tp25207677p25207677.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problem with web service and WTP in Maven multimodule project

[stug23]

Thanks for the tip! I just back to working on this project and have now come
up with a solution, at least partially inspired by your suggestion.

I did try the approach you recommended initially after reading your reply.
However after working through the problem, I ended up with a different
solution with the same outcome.

I used the assembly plugin to create a wsdl artifact containing the wsdl and
related schemas in a zip packaged artifact in the person-service module.

Then I used the dependency:unpack goal in the person-service-web module to
unpack the zip artifact into the src/main/webapp/WEB-INF/wsdl directory. The
unpack approach is nice because it lets you configure such that you can
overwrite the existing files in the target directory.


Stephen Connolly-2 wrote:
> 
> use buildhelper to attach the wsdl as an artifact of person service.
> then add the wsdl as a dependency of the war (type wsdl) then use
> dependecy plugin to copy dependencies with includeType set to wsdl
> 
> that will at least give the most interdependency info to standard
> tools parsing your poms
> 
> might get you somewhere
> On Saturday, June 27, 2009, stug23  wrote:
>>
>> I have a multimodule project for a Sun JAXWS web service and am trying
>> figure
>> out the best way to single source the WSDL and XML Schema files for the
>> project. The project multimodule structure is shown below. I am having
>> issues related to the sourcing of these files when using the Eclipse
>> option
>> menu Run As ==> Run on Server.
>>
>> The WSDL and XML Schema files are currently in the
>> person-service/src/main/wsdl directory. This seems the most logical place
>> to
>> maintain these files, since this is a contract-first service in which the
>> Java code is generated from the WSDL and XML Schema. For modifying the
>> WSDL
>> and/or editing the XML Schema it seems logical to maintain these files in
>> the person-service module.
>>
>> I have initially used the maven-war-plugin to copy the WSDL and XML
>> Schema
>> files from the person-service module to the person-service-web
>> target/person-service-web/WEB-INF/wsdl folder so that these files end up
>> in
>> the Maven-generated war file. However this approach doesn't work for
>> running
>> the person-service-web project using the Eclipse option menu Run As ==>
>> Run
>> on Server. This is apparently because the dynamic publishing feature used
>> by
>> WTP doesn't use the files contained in
>> target/person-service-web/WEB-INF/wsdl.
>>
>> If I copy the WSDL and XML Schema files into
>> person-service-web/src/main/webapp/WEB-INF/wsdl, then the WTP Eclipse
>> option
>> menu Run As ==> Run on Server works correctly -- the WSDL and XML Schema
>> are
>> then available via the web service URL:
>> (http://localhost:8080/person-service-web/PersonService?wsdl).
>>
>> Since I do want to single source the WSDL and XML Schema files (hopefully
>> in
>> the person-service module) is there a better way to accomplish this and
>> still publish correctly for WTP?
>>
>> The modules are:
>>
>> person-service-parent    [pom] --- parent module which contains the
>> following sub-modules:
>>    person-service         [jar] --- contains web service code, WSDL and
>> XML
>> Schema files
>>    person-service-web     [war] --- contains web.xml and sun-jaxws.xml
>> files
>>    person-service-testing [pom] --- module to perform integration testing
>>
>>
>> TIA!
>> --
>> View this message in context:
>> http://www.nabble.com/Problem-with-web-service-and-WTP-in-Maven-multimodule-project-tp24233382p24233382.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-web-service-and-WTP-in-Maven-multimodule-project-tp24233382p24597915.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Problem getting javasvn to work with build number plugin Click to flag this post

[stug23]

Has anyone been successful in getting the javasvn provider for the build
number plugin to work?

I posted this question to codehaus-mojo/mojo-user forum with the details:



TIA!


-- 
View this message in context: 
http://www.nabble.com/Problem-getting-javasvn-to-work-with-build-number-plugin-Click-to-flag-this-post-tp24428652p24428652.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Problem with web service and WTP in Maven multimodule project

[stug23]

I have a multimodule project for a Sun JAXWS web service and am trying figure
out the best way to single source the WSDL and XML Schema files for the
project. The project multimodule structure is shown below. I am having
issues related to the sourcing of these files when using the Eclipse option
menu Run As ==> Run on Server.

The WSDL and XML Schema files are currently in the
person-service/src/main/wsdl directory. This seems the most logical place to
maintain these files, since this is a contract-first service in which the
Java code is generated from the WSDL and XML Schema. For modifying the WSDL
and/or editing the XML Schema it seems logical to maintain these files in
the person-service module.

I have initially used the maven-war-plugin to copy the WSDL and XML Schema
files from the person-service module to the person-service-web
target/person-service-web/WEB-INF/wsdl folder so that these files end up in
the Maven-generated war file. However this approach doesn't work for running
the person-service-web project using the Eclipse option menu Run As ==> Run
on Server. This is apparently because the dynamic publishing feature used by
WTP doesn't use the files contained in
target/person-service-web/WEB-INF/wsdl.

If I copy the WSDL and XML Schema files into
person-service-web/src/main/webapp/WEB-INF/wsdl, then the WTP Eclipse option
menu Run As ==> Run on Server works correctly -- the WSDL and XML Schema are
then available via the web service URL:
(http://localhost:8080/person-service-web/PersonService?wsdl).

Since I do want to single source the WSDL and XML Schema files (hopefully in
the person-service module) is there a better way to accomplish this and
still publish correctly for WTP?

The modules are:

person-service-parent[pom] --- parent module which contains the
following sub-modules:
   person-service [jar] --- contains web service code, WSDL and XML
Schema files
   person-service-web [war] --- contains web.xml and sun-jaxws.xml files
   person-service-testing [pom] --- module to perform integration testing


TIA! 
-- 
View this message in context: 
http://www.nabble.com/Problem-with-web-service-and-WTP-in-Maven-multimodule-project-tp24233382p24233382.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Properties: backslashes in pathname on Windows

[stug23]

I found a Maven plugin at Google that can replace tokens which I applied to
the filtered xml file.

This does remove the backslashes, however I think a much better solution
would be for Maven to have a simple and direct means of obtaining a file:URL
with correct form via a Maven project property.

Perhaps something like ${project.parent.basedir.url}? At this stage a
feature such as this might be more relevant as a Maven 3.0 addition?

Here is an example of using the maven-replacer-plugin configuration that can
replace tokens:


bakersoftware
maven-replacer-plugin
0.0.9


test-compile

replace


target/test-classes/persistence.xml
\\
/






stug23 wrote:
> 
> Is there a way in Maven 2.0.9 to end up with forward slashes in a
> file/directory pathname on the Windows platform when filtering a property
> such as ${project.parent.basedir}?
> 
> I need to supply a file URL for a Hibernate URL specified in a
> persistence.xml configuraton file. The following property statement from a
> persistence.xml file gets filtered as a resource file from
> src/test/resources into the test-classes directory under target.
> 
> However on Windows the pathname ends up including backslashes which don't
> play well with Hibernate. The JPA hibernate entity manager cannot resolve
> a URL with backslashes in it.
> 
> The XML element in questions looks more or less like this:
> 
>  value="jdbc:hsqldb:file:///${project.parent.basedir}/target/hsql/testdb"/>
> 
> Suggestions on how to accomplish this would be appreciated.
> 
> TIA!
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Properties%3A-backslashes-in-pathname-on-Windows-tp23209361p23219538.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Properties: backslashes in pathname on Windows

[stug23]

Is there a way in Maven 2.0.9 to end up with forward slashes in a
file/directory pathname on the Windows platform when filtering a property
such as ${project.parent.basedir}?

I need to supply a file URL for a Hibernate URL specified in a
persistence.xml configuraton file. The following property statement from a
persistence.xml file gets filtered as a resource file from
src/test/resources into the test-classes directory under target.

However on Windows the pathname ends up including backslashes which don't
play well with Hibernate. The JPA hibernate entity manager cannot resolve a
URL with backslashes in it.

The XML element in questions looks more or less like this:



Suggestions on how to accomplish this would be appreciated.

TIA!

-- 
View this message in context: 
http://www.nabble.com/Properties%3A-backslashes-in-pathname-on-Windows-tp23209361p23209361.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Site Plugin 2.0 Released

[stug23]

As of 9:20 am PDT the version 2.0 plugin doesn't appear to have made it to
Maven Central yet:




dennisl-2 wrote:
> 
> The Maven team is pleased to announce the release of the Maven Site
> Plugin, version 2.0
> 
> The Site Plugin is used to generate a site for the project. The
> generated site also includes the project's reports that were configured
> in the  section of the POM.
> 
> http://maven.apache.org/plugins/maven-site-plugin/
> 
> You should specify the version in your project's plugin configuration:
> 
> 
>  org.apache.maven.plugins
>  maven-site-plugin
>  2.0
> 
> 
> 
> Release Notes - Maven 2.x Site Plugin - Version 2.0
> 
> 
> ** Bug
> * [MSITE-129] - modules list empty if modules don't use this project
> as parent in reactor build
> * [MSITE-136] - when inheriting site.xml the 
> expands to a menu with links for *all* ancestors and not just the
> immediate parent
> * [MSITE-150] - Inconsistent navigational mechanisms: If project
> defines its own index page (e.g. apt/index.apt) the Project
> Information->About link is missing.
> * [MSITE-163] - The modules menu is not inherited if the parent
> project has no modules of its own
> * [MSITE-180] - Missing url tag in (parent) pom make it ignore the
> site inheritence system
> * [MSITE-238] - multi project default URL is wrong
> * [MSITE-275] - site:stage  for multimodule project creates wrong
> links
> * [MSITE-311] - NPE on absolute URLs if project.url not defined
> * [MSITE-320] - Reference documentation
> * [MSITE-362] - Site upload is not compatible with sourceforge.net
> changes
> * [MSITE-384] - site:stage-deploy fails on Windows for projects with
> 3 levels of modules
> * [MSITE-386] - site is generated with empty site.css file
> 
> ** Improvement
> * [MSITE-132] - Use  instead of  for staged
> directories
> * [MSITE-287] - Clarify/fix documentation about encoding for
> translated resource bundles.
> * [MSITE-349] - Update this plugin's site documentation page:
> "Configuring the Site Descriptor" to include the  element
> * [MSITE-350] - site:deploy not verbose enough, not, _at all_ with -X
> * [MSITE-351] - New language - Portuguese (Portugal)
> * [MSITE-352] - Link to L10n Status Report for Project Info Reports
> Plugin
> * [MSITE-382] - Add localization for  zh_TW
> 
> ** New Feature
> * [MSITE-340] - use ${project.reporting.outputEncoding} as default
> value for "outputEncoding" parameter and default to UTF-8
> 
> ** Task
> * [MSITE-101] - schedule and release doxia 1.0
> * [MSITE-242] - remove copy of plexus-utils sources from site plugin
> sources since it is a dependency
> * [MSITE-355] - Upgrade to Wagon 1.0-beta-4
> * [MSITE-388] - Update to maven-doxia-tools 1.0.2
> 
> 
> Enjoy,
> 
> -The Maven team
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-ANN--Maven-Site-Plugin-2.0-Released-tp22458511p22458844.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Question on the dependency plugin

[stug23]

Thanks Brian. That solved my problem.

I did find that since I wanted both .class and source jar files that the
best approach was to have two executions of the dependency plugin. And since
not all source jars are available I added a failOnMissingClassifierArtifact
= false to help things along.

Here is my configuration for the dependency plugin that worked successfully:


org.apache.maven.plugins
maven-dependency-plugin
2.0


copy-jars
package

copy-dependencies

false


copy-sources
install

copy-dependencies



${project.build.directory}/dependency-sources
sources

false


false





Brian E Fox wrote:
> 
> This is a bit confusing and I had to refresh myself with the code.
> 
> The includeClassifier will filter the list based on the classifier.
> Unless you have declared dependencies on sources jars, they won't be
> included by your config below. If you want the dependencies to be
> translated into sources jars and then resolved/copied, instead set
> sources and that should do it for you.
> 
> See below:
> 
> // transform artifacts if classifier is set
> DependencyStatusSets status = null;
> if ( StringUtils.isNotEmpty( classifier ) )
> {
> status = getClassifierTranslatedDependencies( artifacts,
> stopOnFailure );
> }
> else
> {
> status = filterMarkedDependencies( artifacts );
> }
> 
> -Original Message-
> From: stug23 [mailto:pat.poden...@gmail.com] 
> Sent: Wednesday, January 07, 2009 6:30 PM
> To: users@maven.apache.org
> Subject: Question on the dependency plugin
> 
> 
> I am trying to figure out how to use dependency plugin to copy both
> .class
> jar files as well as source jars.
> 
> Unfortunately, so far I only able to copy the .class jar files, but the
> source jars (which I know are available for my artifacts) do not get
> copied.
> 
> Please have a look at my plugin configuration and tell me what I'm doing
> wrong. Note that I have tried declaring the includeClassifiers element
> both
> inside and outside the execution element with no success.
> 
> Here is my plugin configuration:
> 
> 
>   org.apache.maven.plugins
>   maven-dependency-plugin
>   2.0
>   
>   sources
>   
>   
>   
>   
>   install
>   
>   copy-dependencies
>   
>   false
>   
>   
> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Question-on-the-dependency-plugin-tp21342783p21342
> 783.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Question-on-the-dependency-plugin-tp21342783p21356664.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Question on the dependency plugin

[stug23]

I am trying to figure out how to use dependency plugin to copy both .class
jar files as well as source jars.

Unfortunately, so far I only able to copy the .class jar files, but the
source jars (which I know are available for my artifacts) do not get copied.

Please have a look at my plugin configuration and tell me what I'm doing
wrong. Note that I have tried declaring the includeClassifiers element both
inside and outside the execution element with no success.

Here is my plugin configuration:


org.apache.maven.plugins
maven-dependency-plugin
2.0

sources




install

copy-dependencies

false




-- 
View this message in context: 
http://www.nabble.com/Question-on-the-dependency-plugin-tp21342783p21342783.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Is there a way to also copy source jars using dependency plugin?

[stug23]

Our project has written a "jar extractor" that uses the dependency plugin to
build a directory of jars from the Maven repository for a project. These
jars are to be used by a non-Maven project (which eventually will be
converted to Maven, only not yet). We would also like to include the source
jars associated with the same compile artifacts.

Is there a way to also copy source jars using dependency plugin?

TIA

-- 
View this message in context: 
http://www.nabble.com/Is-there-a-way-to-also-copy-source-jars-using-dependency-plugin--tp20905839p20905839.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Advice on version conventions for parallel, multi-team development

[stug23]

Am I the only one with this question?


stug23 wrote:
> 
> My question is related to the situation where there are multiple teams
> working on the same project. Let's call the project 'foo-bar'
> 
> For example, Team A is working on a Subversion branch called 'team-a' and
> Team B is working on another Subversion branch called 'team-b'.
> 
> The builds are automatically deployed to a shared Maven repo via Hudson
> build jobs. So there is a Hudson build job watching Team A's branch and
> another job watching Team B's branch. Obviously the two Maven builds will
> need to have different versions in order to make this work so that the
> deployed artifacts are distinct. These build jobs are of course working
> with SNAPSHOT versions.
> 
> So what is a good convention for this? Would something like this make
> sense?
> 
> Team A ==> com.foo:foo-bar:1.0-team-a-SNAPSHOT
> 
> Team B ==> com.foo:foo-bar:1.0-team-b-SNAPSHOT
> 
> Ultimately each of the separate Teams will merge/reintegrate their work
> back onto the trunk. At this point they would need to "clean up" their
> versions. For example,
> 
> Team A finishes their work and reintegrates onto trunk with a final
> version of:
> 
> com.foo:foo-bar:1.0-SNAPSHOT
> 
> Some time later Team B finishes their work and reintegrates onto trunk
> with a final version of:
> 
> com.foo:foo-bar:1.0-SNAPSHOT
> 
> Then we release from trunk as:
> 
> com.foo:foo-bar:1.0
> 
> Does this make sense? Or is there a better way to handle this parallel
> development scenario?
> 
> TIA
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Advice-on-version-conventions-for-parallel%2C-multi-team-development-tp20490312p20529587.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Advice on version conventions for parallel, multi-team development

[stug23]

My question is related to the situation where there are multiple teams
working on the same project. Let's call the project 'foo-bar'

For example, Team A is working on a Subversion branch called 'team-a' and
Team B is working on another Subversion branch called 'team-b'.

The builds are automatically deployed to a shared Maven repo via Hudson
build jobs. So there is a Hudson build job watching Team A's branch and
another job watching Team B's branch. Obviously the two Maven builds will
need to have different versions in order to make this work so that the
deployed artifacts are distinct. These build jobs are of course working with
SNAPSHOT versions.

So what is a good convention for this? Would something like this make sense?

Team A ==> com.foo:foo-bar:1.0-team-a-SNAPSHOT

Team B ==> com.foo:foo-bar:1.0-team-b-SNAPSHOT

Ultimately each of the separate Teams will merge/reintegrate their work back
onto the trunk. At this point they would need to "clean up" their versions.
For example,

Team A finishes their work and reintegrates onto trunk with a final version
of:

com.foo:foo-bar:1.0-SNAPSHOT

Some time later Team B finishes their work and reintegrates onto trunk with
a final version of:

com.foo:foo-bar:1.0-SNAPSHOT

Then we release from trunk as:

com.foo:foo-bar:1.0

Does this make sense? Or is there a better way to handle this parallel
development scenario?

TIA



-- 
View this message in context: 
http://www.nabble.com/Advice-on-version-conventions-for-parallel%2C-multi-team-development-tp20490312p20490312.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Crash when running site:site

[stug23]

I have a Maven project that's not very large or complex, however when I run
mvn site a fatal out of memory error occurs. I am enclosing the last portion
of the console output as an attached file.

When the job reaches the line '[INFO] Generating "Dependencies" report.' it
runs for a long time at high CPU level and then crashes.
http://www.nabble.com/file/p20465863/mvn-site-error.txt mvn-site-error.txt 

When encountering this problem does anyone have suggestions as to how to
diagnose the problem?

Do I just have to give this more heap? Or is there some other underlying
problem that needs to be addressed? My other Maven jobs don't encounter this
error even though some of these projects are larger and more complex.
-- 
View this message in context: 
http://www.nabble.com/Crash-when-running-site%3Asite-tp20465863p20465863.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Parametrizing directory names in an archetype

[stug23]

The 2.0-alpha-4 archetype plugin can do this for filenames -- I haven't tried
it with directory names, however this definitely works for sub module
directories so I think it will work in the general case.

The syntax for your example is (double underscore before and after the
property name):

resources/archetype-resources/src/test/java/__param1__/App.java

And you will need to use this in the meta data file as well.

For more info see



and 







Bugzilla from [EMAIL PROTECTED] wrote:
> 
> Hello!
> 
> The question ist the following: can I somehow achieve that directory names
> in the project generated with the archetype are passed as parameters? I'm
> talking about something like this:
> 
> In the archetype:
> resources/archetype-resources/src/test/java/$param1/App.java
> 
> Then you could generate your project like
> mvn archetype:generate ... -Dparam1=serverutils
> 
> and you would end up having a directory + file like
> src/test/java/serverutils/App.java
> 
> 
> Is that possible with the archetype plug-in?
> 
> Thanks,
> Agoston
> 
> 
> 
>   
> 

-- 
View this message in context: 
http://www.nabble.com/Parametrizing-directory-names-in-an-archetype-tp20378844p20392518.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Status of repo1.maven.org

[stug23]

Here is another update from Slashdot regarding the problem between Sprint and
Cogent:

   

Of course all of this is interesting for folks to discuss and debate .
however the real question is: 

"What are those of us that have been cutoff from Maven Central Repo
supposed to do?"

Is the best solution to point at one of the mirrors in another country? Or?

   



KC Baltz wrote:
> 
> The problem is likely caused by a legal issue between Sprint and Cogent.  
> 
> http://tinyurl.com/5gnysk
> 
>> On October 30 at 4:30 pm Sprint-Nextel severed its Internet connection 
>> to Cogent thereby partitioning the Internet.
>> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Status-of-repo1.maven.org-tp20270490p20296850.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Status of repo1.maven.org

[stug23]

I just verified that I can NOT get to either of the ibiblio mirrors in the US
(I am located in the Pacific Northwest).

However I can get to the Chinese, Danish and Spanish mirrors.

Mirrors Repositories
   <http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories>



stug23 wrote:
> 
> As of 12:55 PM PDT I am able to access Maven Central from my iPhone via
> EDGE network, but not via my company's internal network via proxy.
> 
> I am guessing that the problem lies somewhere in the network cloud such
> that some network providers are accessible and some are not.
> 
> 
> 
> mclark_114 wrote:
>> 
>> Does anyone know what he status of repo1.maven.org is. It appears to be
>> non-responsive.
>> 
>>  
>> 
>> -Mclark
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Status-of-repo1.maven.org-tp20270490p20273454.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Status of repo1.maven.org

[stug23]

As of 12:55 PM PDT I am able to access Maven Central from my iPhone via EDGE
network, but not via my company's internal network via proxy.

I am guessing that the problem lies somewhere in the network cloud such that
some network providers are accessible and some are not.



mclark_114 wrote:
> 
> Does anyone know what he status of repo1.maven.org is. It appears to be
> non-responsive.
> 
>  
> 
> -Mclark
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Status-of-repo1.maven.org-tp20270490p20273130.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Multimodule archetype does not propagate the artifactId in module names

[stug23]

Raphaël,

It turned out that the generated archetype that was attached to
http://jira.codehaus.org/browse/ARCHETYPE-153 was the problem.

When I started with the project and ran archetype:create-from-project on it,
the resultant generated archetype worked correctly.

Thanks,

Pat


 

Raphaël wrote:
> 
> Thanks for all these inforations
> 
> Raphaël
> 
> 2008/10/27 stug23 <[EMAIL PROTECTED]>:
>>
>> After further testing, it appears that the problems I have with
>> multimodule
>> projects do not occur on the Windows platform, just on Mac OS X. I will
>> do
>> some more testing to nail this down.
>>
>>
>>
>> stug23 wrote:
>>>
>>> Archetype NG is supposed to work properly with multimodule projects
>>> however I just tested it and found that it is not working.
>>>
>>> I added a comment to the original JIRA:
>>>
>>> http://jira.codehaus.org/browse/ARCHETYPE-153
>>>
>>> This feature is one that I need for projects in the near term and I
>>> would
>>> appreciate it if Maven experts here could help with resolving this
>>> problem.
>>>
>>> TIA
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Multimodule-archetype-does-not-propagate-the-artifactId-in-module-names-tp20170155p20190686.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multimodule-archetype-does-not-propagate-the-artifactId-in-module-names-tp20170155p20220991.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Multimodule archetype does not propagate the artifactId in module names

[stug23]

After further testing, it appears that the problems I have with multimodule
projects do not occur on the Windows platform, just on Mac OS X. I will do
some more testing to nail this down.



stug23 wrote:
> 
> Archetype NG is supposed to work properly with multimodule projects
> however I just tested it and found that it is not working. 
> 
> I added a comment to the original JIRA:
> 
> http://jira.codehaus.org/browse/ARCHETYPE-153
> 
> This feature is one that I need for projects in the near term and I would
> appreciate it if Maven experts here could help with resolving this
> problem.
> 
> TIA
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multimodule-archetype-does-not-propagate-the-artifactId-in-module-names-tp20170155p20190686.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Multimodule archetype does not propagate the artifactId in module names

[stug23]

Archetype NG is supposed to work properly with multimodule projects however I
just tested it and found that it is now working. 

I added a comment to the original JIRA:

http://jira.codehaus.org/browse/ARCHETYPE-153

This feature is one that I need for projects in the near term and I would
appreciate it if Maven experts here could help with resolving this problem.

TIA


-- 
View this message in context: 
http://www.nabble.com/Multimodule-archetype-does-not-propagate-the-artifactId-in-module-names-tp20170155p20170155.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Multiple executions of goals under generate-sources: How to avoid?

[stug23]

Lacking any other solution I went ahead and incorporated an internal Maven
property that gets set at the end of the first code generation in the
lifecycle. That way subsequent checks of the property provide an indication
to skip code generation.

This seems kind of kludgy but it works 



stug23 wrote:
> 
> As a clarification, the execution that I am trying to avoid is the second
> execution of a code generator mojo that is bound to generate-sources
> phase.
> 
> The second execution results from uses the maven-sources-plugin which
> states:
> 
> "Invokes the execution of the lifecycle phase generate-sources prior to
> executing itself."
> 
> The information above is from the following reference:
> 
> <http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html>
> 
> So my question is: "Is there a way to still produce a sources jar using
> the maven-source-plugin without invoking execution of the generate-sources
> phase?"
> 
> It doesn't make sense to me that this invocation cannot be switched off
> since the code generation has already taken place and  it's not very
> efficient to perform code generation all over again in a subsequent
> lifecycle phase. Perhaps there are cases where this is needed, but mine is
> not one of them, so I am hoping that someone can help me to disable this
> feature of the maven-source-plugin.
> 
> TIA
> 
> 
> 
> 
> stug23 wrote:
>> 
>> I am working on a code generator plugin that ends up being executed
>> multiple times when in fact I only want it to execute once in the
>> generate-sources phase.
>> 
>> According to this posting
>> <http://www.mail-archive.com/users@maven.apache.org/msg78484.html> this
>> is an expected behavior.
>> 
>> How do I avoid multiple executions of my code generator which needs to
>> run in the generate-sources phase?
>> 
>> TIA
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multiple-executions-of-goals-under-generate-sources%3A-How-to-avoid--tp20038097p20057662.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Multiple executions of goals under generate-sources: How to avoid?

[stug23]

As a clarification, the execution that I am trying to avoid is the second
execution of a code generator mojo that is bound to generate-sources phase.

The second execution results from uses the maven-sources-plugin which
states:

"Invokes the execution of the lifecycle phase generate-sources prior to
executing itself."

The information above is from the following reference:

<http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html>

So my question is: "Is there a way to still produce a sources jar using the
maven-source-plugin without invoking execution of the generate-sources
phase?"

It doesn't make sense to me that this invocation cannot be switched off
since the code generation has already taken place and  it's not very
efficient to perform code generation all over again in a subsequent
lifecycle phase. Perhaps there are cases where this is needed, but mine is
not one of them, so I am hoping that someone can help me to disable this
feature of the maven-source-plugin.

TIA




stug23 wrote:
> 
> I am working on a code generator plugin that ends up being executed
> multiple times when in fact I only want it to execute once in the
> generate-sources phase.
> 
> According to this posting
> <http://www.mail-archive.com/users@maven.apache.org/msg78484.html> this is
> an expected behavior.
> 
> How do I avoid multiple executions of my code generator which needs to run
> in the generate-sources phase?
> 
> TIA
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multiple-executions-of-goals-under-generate-sources%3A-How-to-avoid--tp20038097p20047618.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Multiple executions of goals under generate-sources: How to avoid?

[stug23]

I am working on a code generator plugin that ends up being executed multiple
times when in fact I only want it to execute once in the generate-sources
phase.

According to this posting
 this is
an expected behavior.

How do I avoid multiple executions of my code generator which needs to run
in the generate-sources phase?

TIA

-- 
View this message in context: 
http://www.nabble.com/Multiple-executions-of-goals-under-generate-sources%3A-How-to-avoid--tp20038097p20038097.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Using a property from a mojo in subsequent plugin executions

[stug23]

Thanks for the tip!

There appear to be a number of good tips for mojo programming in the mojo
developer cookbook. I was able to immediately take advantage of the
MavenProject object to set a property from a mojo for use by other plugins
later in the lifecycle.



Wayne Fay wrote:
> 
> You can add a property via MavenProject, see the Mojo Developer Cookbook
> here:
> http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook
> 
> Wayne
> 
> On Mon, Oct 13, 2008 at 9:04 AM, stug23 <[EMAIL PROTECTED]> wrote:
>>
>> Is there a standard way to access a property that was set/established
>> within
>> a mojo in other, different plugin executions in the same POM?
>>
>> My use case is one where a mojo determines the value for a property that
>> was
>> not set/input to the mojo. This property needs to be available to other
>> plugins for execution within the same lifecycle in later phases. I was
>> able
>> to stuff the property into System.setProperty("key",value) however I was
>> wondering if there is a better way to do this?
>>
>> Or is the only way to make this work via filtering and writing to files?
>>
>> TIA
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Using-a-property-from-a-mojo-in-subsequent-plugin-executions-tp19957750p19957750.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Using-a-property-from-a-mojo-in-subsequent-plugin-executions-tp19957750p19966249.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Using a property from a mojo in subsequent plugin executions

[stug23]

Is there a standard way to access a property that was set/established within
a mojo in other, different plugin executions in the same POM?

My use case is one where a mojo determines the value for a property that was
not set/input to the mojo. This property needs to be available to other
plugins for execution within the same lifecycle in later phases. I was able
to stuff the property into System.setProperty("key",value) however I was
wondering if there is a better way to do this?

Or is the only way to make this work via filtering and writing to files?

TIA

-- 
View this message in context: 
http://www.nabble.com/Using-a-property-from-a-mojo-in-subsequent-plugin-executions-tp19957750p19957750.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

How do I exclude an xml file from a jar?

[stug23]

I need to have persistence.xml file on the classpath in order to perform DDL
generation using the Hibernate Tool hbm2ddl.

However I don't want the persistence.xml file to be included in the jar
file.

How can I exclude persistence.xml from the jar file even though it needs to
be on the classpath earlier in the lifecycle?

TIA
-- 
View this message in context: 
http://www.nabble.com/How-do-I-exclude-an-xml-file-from-a-jar--tp19902363p19902363.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

URL encoding issues on Windows platform

[stug23]

One of our developers is using the exec:java plugin to launch a Java
application. Within the application the JBoss Microcontainer is used and a
java.net.MalformedURLException occurs.

Apparently this is a known problem:

  


However the workaround recommended in the reference above is to move the
local .m2 repo to a directory with no spaces in the pathname. This seems
like a drastic approach to me.

Does anyone here know of a way to use Spring and the JBoss Microcontainer on
a Windows platform without having to move the .m2 repo?

TIA
-- 
View this message in context: 
http://www.nabble.com/URL-encoding-issues-on-Windows-platform-tp19901546p19901546.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Best Practice for code generation scenarios in Maven

[stug23]

Thanks I'll take a look at how jaxb maven plugin does this.

Is there really a difference in what you are recommending? When you say 'new
directory' don't you just mean somewhere under target (e.g.,
target/codegen/java)?


Michael McCallum-3 wrote:
> 
> no you should generate into a new directory and add it as a source compile 
> root...
> 
> attach he plugin to generate-sources and it will be compiled and jar'd up
> just 
> like other code...
> 
> see the jaxb2 or xmlbeans plugins for examples...
> 
> On Wed, 24 Sep 2008 10:16:48 stug23 wrote:
>> I am currently porting an Ant-powered code generator to Maven and would
>> like to get input from this group for best practices with respect to code
>> generation in Maven.
>>
>> Let's see if I have this right:
>>
>> I wrote a Maven mojo to drive the code generator and can configure it in
>> the Maven project used for code generation.
>>
>> I should always isolate the code generation into a single Maven module
>> (this could be part of a multi-module Maven project though) so that I can
>> declare the source directory for the generated code under the target
>> directory.
>>
>> For example, something like this would be declared in the module where
>> code
>> generation takes place:
>>
>> 
>>
>> ${project.build.directory}/codegen/java
>>...
>>...
>>
>> The jar file artifact resulting from the code generation module would
>> only
>> contain class files from the generator.
>>
>> Since the standard src/main/java  has been 'usurped' by
>> the source directory where the code generator wrote its code, I shouldn't
>> have any other Java code under src/main/java.
>>
>> Does this sound correct? Is this the best practice for a Maven module for
>> code generation? Does anyone on this group do this differently than what
>> I
>> sketched out here? If so, why and what are the advantages of your
>> alternative approach?
>>
>> Thanks in advance for your input!
>>
>> :handshake:
> 
> 
> 
> -- 
> Michael McCallum
> Enterprise Engineer
> mailto:[EMAIL PROTECTED]
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Best-Practice-for-code-generation-scenarios-in-Maven-tp19638243p19651141.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Best Practice for code generation scenarios in Maven

[stug23]

Thanks for the tip on the build helper plugin. This makes setting the
generated source more sensible than just altering sourceDirectory.



newton.dave wrote:
> 
> --- On Tue, 9/23/08, stug23 wrote:
>> Does anyone on this group do this differently than what I
>> sketched out here? If so, why and what are the advantages
>> of your alternative approach?
> 
> I'm currently generating source into various /target/generated-sources
> sub-directories and using the build-helper plugin to add source trees.
> 
> The module contains sub-classes of the generated classes and (famous last
> words) we don't have any reason to provide the base classes as their own
> artifact. For now, anyway, keeping things together seemed better.
> 
> The only real advantage, and it seems slim, is that of locality and
> cohesiveness.
> 
> Dave
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Best-Practice-for-code-generation-scenarios-in-Maven-tp19638243p19651094.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Best Practice for code generation scenarios in Maven

[stug23]

I am currently porting an Ant-powered code generator to Maven and would like
to get input from this group for best practices with respect to code
generation in Maven.

Let's see if I have this right:

I wrote a Maven mojo to drive the code generator and can configure it in the
Maven project used for code generation.

I should always isolate the code generation into a single Maven module (this
could be part of a multi-module Maven project though) so that I can declare
the source directory for the generated code under the target directory.

For example, something like this would be declared in the module where code
generation takes place:


  
${project.build.directory}/codegen/java
   ...
   ...

The jar file artifact resulting from the code generation module would only
contain class files from the generator.

Since the standard src/main/java  has been 'usurped' by
the source directory where the code generator wrote its code, I shouldn't
have any other Java code under src/main/java.

Does this sound correct? Is this the best practice for a Maven module for
code generation? Does anyone on this group do this differently than what I
sketched out here? If so, why and what are the advantages of your
alternative approach?

Thanks in advance for your input!

:handshake:



-- 
View this message in context: 
http://www.nabble.com/Best-Practice-for-code-generation-scenarios-in-Maven-tp19638243p19638243.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Maven/Eclipse - Keeping them in sync?

[stug23]

To bring project up to date when adding source directories, try selecting the
following menu item from the contextual menu (right-click on your project in
the Package Explorer):

Maven => Update Project Configuration

This will synch up the source folders with the Eclipse classpath.



David C. Hicks wrote:
> 
> OK, I installed m2eclipse and it seems happy with my project. I was able 
> to go through the POM editor and update a lot of information that 
> previously wasn't there. Very cool.
> 
> Problem: I still don't see it picking up new source folders. If I add a 
> source folder in Eclipse, how does that end up in the pom.xml to somehow 
> be included in a production and/or test build? I see a spot to enter 
> source folders in the POM editor, but it is unclear how to actually 
> enter them.
> 
> Am I missing something?
> 
> Thanks again!
> Dave
> 
> PS - for those who recommended Q4E, I'm looking at it, too, but from 
> what I can tell it seems that m2eclipse is way ahead in terms of fit and 
> finish. That's just a first impression, though.
> 
> 
> Stevo Slavic' wrote:
>> Hello David,
>>
>> Just as Klaus said, use m2eclipse plugin. After installing it, I'd first
>> manually create a folder in eclipse workspace, named as your root maven
>> project artifactId, then copy root POM and rest of the project structure
>> you've created into that new folder. Finally, with m2eclipse plugin you
>> could just "File-->Import...-->General-->Maven Projects" and
>> select/browse
>> to newly created folder, leaving m2eclipse do the rest.
>>
>> Regards,
>> Stevo.
>>
>> On Fri, Sep 19, 2008 at 11:24 PM, Klaus <[EMAIL PROTECTED]> wrote:
>>
>>   
>>> Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin
>>> that
>>> updates the project settings according to the setting in the pom.xml. No
>>> (re)generate of eclipse-project files, no problem with new source
>>> folders..
>>>
>>> klaus
>>>
>>> On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> 
 I'm beginning a new, fairly large, project.  Eclipse will be our
 development platform, but I've already set up the starting point in
   
>>> Maven.
>>> 
  Simple enough.  Now, my question is, how can I keep them in sync,
   
>>> easily?
>>> 
  I realize that it's best to re-run "mvn eclipse:eclipse" after adding
 dependencies, but what about source folders?  I need to add new source
 folders, but Maven doesn't know anything about that, so the next time I
 re-generate the .project/.classpath files, it'll revert back to those
 folders not being "source" folders.

 Any help how to make this behave?
 Thanks,
 Dave


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


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

-- 
View this message in context: 
http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19582428.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Renaming a file during creation of a project from an archetype

[stug23]

Is there an automated way to rename a file contained in an archetype during
project creation? For example if the archetype were for a web service it
might have a file in WEB-INF/wsdl/ named 'FooService.wsdl'.

The objective would to rename the file 'FooService.wsdl' based on the
artifactId of the created project. For example, 'FooService.wsdl' might be
renamed as 'LotteryService.wsdl' during project creation from the archetype.


-- 
View this message in context: 
http://www.nabble.com/Renaming-a-file-during-creation-of-a-project-from-an-archetype-tp18933073p18933073.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Maven 'deploy' relationship to large-scale software deployment

[stug23]

Yes I have found that Cargo has some nice capabilities for deploying into
remote containers, along with the war merging capability to address cases
where services and/or other components need to be combined in certain
deployments.

I do find it interesting that there aren't more tools (well as far as I am
aware at this point...) that are designed specifically to perform
large-scale deployment from a Maven repository to multiple (in some cases
many ~100s) destinations.

With respect to your posting on configuration, I totally agree -- it just
makes sense to separate configuration from the jars/wars/ears to the
greatest extent possible. It's much easier to configure for a site when it
doesn't involve ripping apart jars/wars/ears in order to accomplish
site-specific configurations. It can become quite unmanageable to build the
same war file over and over again just to accommodate a couple of tweaks in
an XML configuration file.

Thanks for the replies thus far to my original question! 

Has anyone else out there got more examples of tools that extract from Maven
repository and then construct large-scale deployments to multiple sites?





Brett Porter wrote:
> 
> I think you'll find that Maven itself stops at the repository. So the
> best thing to do is to use tools that can take artifacts from the
> repository and deploy them.
> 
> There are lots of other solutions around for doing this sort of thing
> beyond that point and they specialise in handling the new set of
> problems it brings. I've generally found those doing the deployment
> are very separate from the rest of the development team and often have
> their own chosen set of tooling.
> 
> You could use Maven itself to do this - though I'm not aware of any
> plugins that focus on this. While Cargo is generally used for test
> setups, it could serve this purpose as well, but it's mostly a space
> for a new piece of work.
> 
> Cheers,
> Brett
> 
> 2008/8/1 EJ Ciramella <[EMAIL PROTECTED]>:
>> No, I don't understand how to do it either.  I just stepped out of a
>> meeting where we were discussing how we can deploy the same set of
>> applications (which _some_ share properties) across 10 - 15 different
>> environments.  Some environments have different configurations, some are
>> carbon copies.
>>
>> There doesn't seem to be any maven solution to either/all of these
>> problems:
>>
>> 1 - Where does a property go (say db connection string) that's shared
>> between different applications such that there isn't duplication?  No
>> one wants to have to search/replace values in various profiles.xml or
>> pom.xml files (I don't mind, but others in the organization have
>> objected).  Here, since there are so many applications pointed at the
>> same db, that could be a dozen or so files that have the same db string.
>>
>> 2 - How does one deploy said generated application zip/tar file?
>> There's nothing I can see supplied in any plugin to support large scale
>> deployments (say, six app servers, four web servers, a db server, a
>> utils server and another half dozen or so third party servers).  We've
>> been using ant and a internally written shell script.
>>
>> 3 - How do people configure these things?  I've heard every answer from
>> "we generate a zipped/tarred up application file for every environment"
>> to "we use installshield and don't have to worry" and everything in
>> between.  We have in one environment alone, 6 jboss servers for ONE
>> application.  That ear that gets deployed there (and all it's supporting
>> files) even compressed in a zip takes close to 200 mb.  I'm not about to
>> generate 1200 mb worth of ear files with each build (sometimes there's
>> three or more built in a single day).
>>
>> I feel like either there are different terms to describe these things or
>> no one is doing anything to this scale.
>>
>> I'd love some feedback/suggestions as to how others are doing this.
>>
>> -Original Message-
>> From: stug23 [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, July 31, 2008 10:25 AM
>> To: users@maven.apache.org
>> Subject: Re: Maven 'deploy' relationship to large-scale software
>> deployment
>>
>>
>> Am I alone in needing to understand how Maven relates to large-scale
>> software
>> deployment?
>>
>>   :confused:
>>
>>
>> stug23 wrote:
>>>
>>> Maven has its own notion of 'deploying' a software artifact to a Maven
>>> repository. And there are quite a number of 'out of band' Maven
>

Re: Maven 'deploy' relationship to large-scale software deployment

[stug23]

Am I alone in needing to understand how Maven relates to large-scale software
deployment?

   :confused:


stug23 wrote:
> 
> Maven has its own notion of 'deploying' a software artifact to a Maven
> repository. And there are quite a number of 'out of band' Maven plugins
> such as Cargo that can remotely deploy a war file to a running web
> container.
> 
> My question centers on how Maven relates to situations where once a
> software system has been built and tested, the software components then
> need to be globally distributed to many sites. This notion of 'deploying'
> would appear to be quite different than the one embodied in Maven's deploy
> goal.
> 
> What experiences have developers here had in leveraging Maven for
> large-scale deployments? When did you  stop using Maven and resort to
> other solutions for deploying bundled software to many distributed sites?
> Or were you able to use Maven for your large-scale software deployment
> right out to the sites?
> 
> I would be interested in comments on how others have dealt with this part
> of software deployment. My use case involves distributing 10s of SOA
> services and web applications to many sites.
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-%27deploy%27-relationship-to-large-scale-software-deployment-tp18717756p18755789.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Maven 'deploy' relationship to large-scale software deployment

[stug23]

Maven has its own notion of 'deploying' a software artifact to a Maven
repository. And there are quite a number of 'out of band' Maven plugins such
as Cargo that can remotely deploy a war file to a running web container.

My question centers on how Maven relates to situations where once a software
system has been built and tested, the software components then need to be
globally distributed to many sites. This notion of 'deploying' would appear
to be quite different than the one embodied in Maven's deploy goal.

What experiences have developers here had in leveraging Maven for
large-scale deployments? When did you  stop using Maven and resort to other
solutions for deploying bundled software to many distributed sites? Or were
you able to use Maven for your large-scale software deployment right out to
the sites?

I would be interested in comments on how others have dealt with this part of
software deployment. My use case involves distributing 10s of SOA services
and web applications to many sites.
-- 
View this message in context: 
http://www.nabble.com/Maven-%27deploy%27-relationship-to-large-scale-software-deployment-tp18717756p18717756.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: How to construct an archetype for multi-module build with renamed modules

[stug23]

Raphaël,

>From the transcript in JIRA ARCHETYPE-153 this appears to represent the
feature that I have requested. I wasn't able to run the example due to the
2.0-alpha-3-SNAPSHOT which isn't in the Maven Central repository.

If I understand what you did correctly, you simply specified an artifactId
as pro instead of proficio which should result in creating modules with the
prefix pro instead of proficio.

It was interesting to note that although the build reports an
ArchetypeGenerationFailure, the summary still indicated a successful build?

Thanks for your response!

Is this feature very difficult to add to the archetype plugin?



Raphaël wrote:
> 
> Hi Pat,
> 
> I created http://jira.codehaus.org/browse/ARCHETYPE-153
> Please comment if this issue does not correspond to your issue.
> 
> Regards,
> 
> Raphaël
> 
> 2008/3/24, stug23 <[EMAIL PROTECTED]>:
>>
>>  Based on the lack of response to my posting, is this question too
>> esoteric
>>  for Maven experts to answer?
>>
>>  I have spent a fair amount of time learning about how to use archetypes
>> and
>>  have successfully developed an archetype that uses parameter
>> substitution
>>  with the Velocity templating.
>>
>>  What I am seeking help with here is a way to rename the folders in the
>>  archetype modules based on artifactId when the new project(s) are
>> generated
>>  from the archetype.
>>
>>  Can someone point me to documentation on the new archchetype NG that
>> shows
>>  how to use mojos in an archetype development?
>>
>>
>>
>>  stug23 wrote:
>>  >
>>  > I am seeking advice on how to construct an archetype for a
>> multi-module
>>  > build such that the artifactId of each respective module becomes the
>> name
>>  > for the module in the generated directory structure.
>>  >
>>  > The result I am looking for would resemble the naming conventions of
>> the
>>  > Proficio multi-module project in Better Builds with Maven:
>>  >
>>  > proficio
>>  >   proficio-api
>>  >   proficio-cli
>>  >   proficio-core
>>  >   proficio-model
>>  >   proficio-stores
>>  > proficio-store-memory
>>  > proficio-store-xstream
>>  >
>>  > The intended usage of this archetype would be to create new Maven
>>  > multi-module projects in Eclipse such that the project names follow
>> the
>>  > convention shown in the example above. Without this project naming
>> scheme,
>>  > it is quite difficult for a user to understand which projects are
>> related
>>  > to a multi-module build in the Eclipse workspace.
>>  >
>>  > I wasn't sure whether the new archetype NG may have some feature that
>>  > would help to accomplish this, or whether this requires mojos in the
>>  > archetype, or if M2Eclipse can help out with this requirment.
>>  >
>>  > Thanks in advance for tips, pointers or advice on how to accomplish
>> this
>>  > naming scheme.
>>  >
>>  >
>>  >
>>  >
>>
>>  --
>>
>> View this message in context:
>> http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16254209.html
>>
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>>  -
>>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>>  For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16276697.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: How to construct an archetype for multi-module build with renamed modules

[stug23]

Based on the lack of response to my posting, is this question too esoteric
for Maven experts to answer?

I have spent a fair amount of time learning about how to use archetypes and
have successfully developed an archetype that uses parameter substitution
with the Velocity templating.

What I am seeking help with here is a way to rename the folders in the
archetype modules based on artifactId when the new project(s) are generated
from the archetype.

Can someone point me to documentation on the new archchetype NG that shows
how to use mojos in an archetype development?


stug23 wrote:
> 
> I am seeking advice on how to construct an archetype for a multi-module
> build such that the artifactId of each respective module becomes the name
> for the module in the generated directory structure.
> 
> The result I am looking for would resemble the naming conventions of the
> Proficio multi-module project in Better Builds with Maven:
> 
> proficio
>   proficio-api
>   proficio-cli
>   proficio-core
>   proficio-model
>   proficio-stores
> proficio-store-memory
> proficio-store-xstream
> 
> The intended usage of this archetype would be to create new Maven
> multi-module projects in Eclipse such that the project names follow the
> convention shown in the example above. Without this project naming scheme,
> it is quite difficult for a user to understand which projects are related
> to a multi-module build in the Eclipse workspace.
> 
> I wasn't sure whether the new archetype NG may have some feature that
> would help to accomplish this, or whether this requires mojos in the
> archetype, or if M2Eclipse can help out with this requirment.
> 
> Thanks in advance for tips, pointers or advice on how to accomplish this
> naming scheme.
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16254209.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

How to construct an archetype for multi-module build with renamed modules

[stug23]

I am seeking advice on how to construct an archetype for a multi-module build
such that the artifactId of each respective module becomes the name for the
module in the generated directory structure.

The result I am looking for would resemble the naming conventions of the
Proficio multi-module project in Better Builds with Maven:

proficio
  proficio-api
  proficio-cli
  proficio-core
  proficio-model
  proficio-stores
proficio-store-memory
proficio-store-xstream

The intended usage of this archetype would be to create new Maven
multi-module projects in Eclipse such that the project names follow the
convention shown in the example above. Without this project naming scheme,
it is quite difficult for a user to understand which projects are related to
a multi-module build in the Eclipse workspace.

I wasn't sure whether the new archetype NG may have some feature that would
help to accomplish this, or whether this requires mojos in the archetype, or
if M2Eclipse can help out with this requirment.

Thanks in advance for tips, pointers or advice on how to accomplish this
naming scheme.



-- 
View this message in context: 
http://www.nabble.com/How-to-construct-an-archetype-for-multi-module-build-with-renamed-modules-tp16224882s177p16224882.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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