Nabble - Maven

Re: [VOTE] Release Maven Checkstyle plugin version 2.4

2009-11-14T04:32:41Z

Mark Hobson wrote:

> Staging repo:
> https://repository.apache.org/content/repositories/maven-001/
>
> Staging site:
> http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/

+1

Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Maven Developers

Re: Multi Module Project Assembly plugin

2009-11-14T03:59:32Z

Well, I could try.

/Anders

On Sat, Nov 14, 2009 at 07:10, Stephanie Johnson <jstephanie11@...>wrote:

> Explanation and suggestion in the link was not clear and I couldnt find it
> again. Hence came to Maven Users list for any suggestions. Could you please
> continue to take a look?
>
> On Fri, Nov 13, 2009 at 3:35 PM, Anders Hammar <anders@...> wrote:
>
> > Well, if the same issue was reported somewhere else and there is a
> > workaround - go with that!
> >
> > /Anders
> >
> > On Fri, Nov 13, 2009 at 16:19, Stephanie Johnson <jstephanie11@...
> > >wrote:
> >
> > > Added inheritance=true and phase=install, still install doesnt build
> the
> > > assemblies.
> > >
> > > I read about the same issue in some forum last week, did not understand
> > the
> > > explanation correctly. Now trying to find the link, couldnt find it.
> But
> > > there was some reference about parent pom referring to child, child
> > having
> > > reference to parent and that doesnt work well with assemblies. There
> was
> > > some suggestion about writing a separate pom for assemblies alone.
> > >
> > > I have a sample project which can depict this problem. Will sending
> that
> > > help?
> > >
> > > Thanks.
> > >
> > > On Fri, Nov 13, 2009 at 1:00 AM, Anders Hammar <anders@...>
> > wrote:
> > >
> > > > I think what you're missing is making the plugin inherited. You set
> > that
> > > > like this:
> > > > <inherited>true</inherited>
> > > > Check the pom schema (or this page:
> > > >
> > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
> > > )
> > > > for exact syntax.
> > > >
> > > > Also, I noticed that you don't have no id defined for the execution.
> > > > I'm not sure if it's required though.
> > > >
> > > > To see the effective pom, execute
> > > > mvn help:effective-pom
> > > > This is very helpful to see what the child pom will be including
> > > > inheritance and everything. Use that and to make sure that the plugin
> > > > binding really exists in the child module.
> > > >
> > > > /Anders
> > > >
> > > >
> > > > On Thu, Nov 12, 2009 at 20:47, Stephanie Johnson <
> > jstephanie11@...
> > > > >wrote:
> > > >
> > > > > I have attached my parent pom.xml and one of my modules pom.xml.
> > > > > Please take a look.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > On 11/12/09, Anders Hammar <anders@...> wrote:
> > > > > > You mus be doing something wrong. If the plugin is bound
> correctly,
> > > it
> > > > > will
> > > > > > be executed.
> > > > > > If you post the pom snippet we might spot the issue.
> > > > > >
> > > > > > /Anders
> > > > > >
> > > > > > On Thu, Nov 12, 2009 at 19:25, Stephanie Johnson
> > > > > > <jstephanie11@...>wrote:
> > > > > >
> > > > > >> Thanks for your suggestion Anders. But that doesnt seem to work.
> > If
> > > I
> > > > > >> associate my assembly plugin to package phase or install phase
> and
> > > run
> > > > > >> mvn install or mvn package - it does not build my assemblies.
> > > > > >>
> > > > > >> I tried running mvn install first and then running mvn
> > > > > >> assembly:assembly. This generates following error.
> > > > > >>
> > > > > >> [ERROR] BUILD ERROR
> > > > > >> [INFO]
> > > > > >>
> > > >
> > ------------------------------------------------------------------------
> > > > > >> [INFO] Failed to create assembly: Artifact: blaw blaw (included
> by
> > > > > >> module) does not have an artifact with a file. Please ensure the
> > > > > >> package phase is run before the assembly is generated.
> > > > > >>
> > > > > >> This is weird because all the dependencies are built installed
> and
> > > > ready
> > > > > >> to
> > > > > >> use.
> > > > > >>
> > > > > >> Thanks.
> > > > > >>
> > > > > >> On 11/11/09, Anders Hammar <anders@...> wrote:
> > > > > >> > You should bind the assembly plugin to an appropriate phase
> > (such
> > > as
> > > > > >> > 'package'). The, you only need to run
> > > > > >> > mvn install
> > > > > >> >
> > > > > >> > /Anders
> > > > > >> >
> > > > > >> > On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson
> > > > > >> > <jstephanie11@...>wrote:
> > > > > >> >
> > > > > >> >> All,
> > > > > >> >>
> > > > > >> >> I am using Maven 2.0.9 to build a multi module project. I
> have
> > > > > defined
> > > > > >> the
> > > > > >> >> assembly plugin in my parent pom. I can get my assemblies
> built
> > > > using
> > > > > >> >>
> > > > > >> >> mvn install assembly:assemly
> > > > > >> >>
> > > > > >> >> This command runs the tests twice, once during install phase
> > and
> > > > > >> >> another
> > > > > >> >> during assembly. I tried assembly:single but it throws an
> > error.
> > > > Any
> > > > > >> help
> > > > > >> >> to
> > > > > >> >> fix get my assemblies built without running the tests twice
> is
> > > much
> > > > > >> >> appreciated.
> > > > > >> >>
> > > > > >> >> Thanks.
> > > > > >> >>
> > > > > >> >
> > > > > >>
> > > > > >>
> > > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail: users-unsubscribe@...
> > > > > >> For additional commands, e-mail: users-help@...
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@...
> > > > > For additional commands, e-mail: users-help@...
> > > > >
> > > >
> > >
> >
>

From forum: Maven - Users

Re: [VOTE] Release Apache Maven 3.0-alpha-4

2009-11-14T02:54:09Z

On 2009-11-14, at 4:47 AM, Dan Fabulich wrote:

>
> I was waiting until alpha-3 was out to merge in the MNG-3004 branch.
> MNG-3004 passes all ITs, including a few new ITs of the experimental
> multithreaded mode.
>
> Can we recut alpha-4 with MNG-3004 in it?
>

I'd personally still like to see a little more design around the multi-
threading first. We are going to roll out alpha after alpha based on
feedback we get from users to fix common problems first. I think that
is the real priority we have. I honestly do not see the urgent rush to
push this is. If we have fixes for users I want to push those out
first. I want to be cautious about new features. We haven't added any
new features to the core yet. I have 5-10 things on git branches but I
just don't think it's the priority.

Honestly there's not really any public proposal or design to look at,
and I really think that we should try your branch against the
performance framework and make sure everything is ok. I'm not just
doing this with your feature, I've done it with all the ones that I
have. I've refrained from putting in because I want to make sure we
don't ever go backward and I don't think there is anything wrong with
erring on the side of caution and waiting a couple weeks.

We'll probably keep doing 1-2 alphas a week so there isn't going to be
a huge time span you have to wait. I think we need a proposal and I
think that we have to get into the habit of having two other people
review new features at a bare minimum. I don't think this is an
unreasonable approach.

> -Dan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Maven Developers

Re: [VOTE] Release Maven Checkstyle plugin version 2.4

2009-11-14T02:14:44Z

+1

Hervé

Le jeudi 12 novembre 2009, Mark Hobson a écrit :

> Hi,
>
> The big new feature in this release is an upgrade to Checkstyle 5.0,
> which brings Java 5 compatibility.
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&version=15
> 336
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&st
> atus=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-001/
>
> Staging site:
> http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/
> (Wait for sync, or use proxy)
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Maven Developers

Re: Multi-war complex build recommendation request

2009-11-13T23:43:35Z

Please see here for more on the issues I am facing. Looking not so much as an issue fix as there may not be one, but a recommendation. This may give further information, however.

http://netbeans.org/bugzilla/show_bug.cgi?id=154465
http://issues.appfuse.org/browse/APF-645

John Eichelsdorfer
jobbank.com

From forum: Maven - Users

Multi-war complex build recommendation request

2009-11-13T23:32:12Z

I have a project where there are 5 levels of projects (maven modules each) in a pom hierarchy:

CommonLibrary.jar -> CommonMvc.jar -> ProductAndService.war -> ProjectCore.war -> ProjectSpecific_1.war

The idea is that the later war file configuration files currently replace the earlier ones where they conflict. The result of all of this is one war with all of the files unbundled and re-bundled in order along the chain.

Right now I am using the AppFuse's warpath plugin to accomplish this, but there are problems. Netbeans handles it best, but it fails to recognize compilation paths at times. It sometimes fails to recognize Java file changes, but in somewhat of a predictable manner. There is a big chance this build method may breakdown with 3.0 Maven even worse.

What I am asking is, what do you suggest? How do people handle such complex web project compiles where there are commonly replaced configuration files and web oriented files? What do you consider to be a best method if this will not work? What way do you suggest will work with Netbeans effectively?

Looking for suggestions. I am willing to make changes to the project structure to make it work, but hoping to be able to keep the modules separate as I am seeking as much reuse between the tiers as possible. For instance I compile one final build with different features for USA vs another for China.

Thank you for any help. The more detail the better.

JohnE

John Eichelsdorfer
jobbank.com

From forum: Maven - Users

Re: Encrypted Passwords

2009-11-13T22:21:25Z

Hi,

First, yes this is implemented.

Second, the SecretKey is actually generated per user when he is using the Artifactory Web UI. I mean that the password is used to authenticate the user against LDAP, then when going to the user profile page the user can "Unlock" his password using it's personal private key with the same password. Artifactory never store the LDAP password, just the pair private/public key used to decrypt the grabbled text used by the user in the settings.xml and encrypt is clear text password in the UI.

Is that clear? :)

HTH,

Fred.

On Sat, Nov 14, 2009 at 12:51 AM, bman <bpape@...> wrote:

Howdy,

According to the original feature request for encrypted passwords
(http://issues.jfrog.org/jira/browse/RTFACT-1191), the admin user should be
able to set the key value:
The basic concept is to allow an admin user the ability (via Web UI) to set
a secret key value (javax.crypto.SecretKey) to be used for encrypting users
passwords. Once the secret key has been set, the normal user would use the
Web UI to input his password and then generate the encrypted (Triple DES?)
version of the password. The user would then cut-and-paste the encrypted
string into the settings.xml file.
Was this part implemented? If so, how does one go about doing this?

Otherwise, how is the key set and what security controls are around the key?

We are integrating with LDAP, so we just want to be sure our domain
credentials are well protected.

Thanks,
Barry
--
View this message in context: http://old.nabble.com/Encrypted-Passwords-tp26344800p26344800.html
Sent from the Artifactory-Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Artifactory-users mailing list
Artifactory-users@...
https://lists.sourceforge.net/lists/listinfo/artifactory-users

--
Co. Founder and Chief Architect
JFrog Ltd
http://www.jfrog.org/
http://twitter.com/freddy33

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Artifactory-users mailing list
Artifactory-users@...
https://lists.sourceforge.net/lists/listinfo/artifactory-users

From forum: Artifactory-Users

Re: Multi Module Project Assembly plugin

2009-11-13T22:10:48Z

Explanation and suggestion in the link was not clear and I couldnt find it
again. Hence came to Maven Users list for any suggestions. Could you please
continue to take a look?

On Fri, Nov 13, 2009 at 3:35 PM, Anders Hammar <anders@...> wrote:

> Well, if the same issue was reported somewhere else and there is a
> workaround - go with that!
>
> /Anders
>
> On Fri, Nov 13, 2009 at 16:19, Stephanie Johnson <jstephanie11@...
> >wrote:
>
> > Added inheritance=true and phase=install, still install doesnt build the
> > assemblies.
> >
> > I read about the same issue in some forum last week, did not understand
> the
> > explanation correctly. Now trying to find the link, couldnt find it. But
> > there was some reference about parent pom referring to child, child
> having
> > reference to parent and that doesnt work well with assemblies. There was
> > some suggestion about writing a separate pom for assemblies alone.
> >
> > I have a sample project which can depict this problem. Will sending that
> > help?
> >
> > Thanks.
> >
> > On Fri, Nov 13, 2009 at 1:00 AM, Anders Hammar <anders@...>
> wrote:
> >
> > > I think what you're missing is making the plugin inherited. You set
> that
> > > like this:
> > > <inherited>true</inherited>
> > > Check the pom schema (or this page:
> > >
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
> > )
> > > for exact syntax.
> > >
> > > Also, I noticed that you don't have no id defined for the execution.
> > > I'm not sure if it's required though.
> > >
> > > To see the effective pom, execute
> > > mvn help:effective-pom
> > > This is very helpful to see what the child pom will be including
> > > inheritance and everything. Use that and to make sure that the plugin
> > > binding really exists in the child module.
> > >
> > > /Anders
> > >
> > >
> > > On Thu, Nov 12, 2009 at 20:47, Stephanie Johnson <
> jstephanie11@...
> > > >wrote:
> > >
> > > > I have attached my parent pom.xml and one of my modules pom.xml.
> > > > Please take a look.
> > > >
> > > > Thanks.
> > > >
> > > > On 11/12/09, Anders Hammar <anders@...> wrote:
> > > > > You mus be doing something wrong. If the plugin is bound correctly,
> > it
> > > > will
> > > > > be executed.
> > > > > If you post the pom snippet we might spot the issue.
> > > > >
> > > > > /Anders
> > > > >
> > > > > On Thu, Nov 12, 2009 at 19:25, Stephanie Johnson
> > > > > <jstephanie11@...>wrote:
> > > > >
> > > > >> Thanks for your suggestion Anders. But that doesnt seem to work.
> If
> > I
> > > > >> associate my assembly plugin to package phase or install phase and
> > run
> > > > >> mvn install or mvn package - it does not build my assemblies.
> > > > >>
> > > > >> I tried running mvn install first and then running mvn
> > > > >> assembly:assembly. This generates following error.
> > > > >>
> > > > >> [ERROR] BUILD ERROR
> > > > >> [INFO]
> > > > >>
> > >
> ------------------------------------------------------------------------
> > > > >> [INFO] Failed to create assembly: Artifact: blaw blaw (included by
> > > > >> module) does not have an artifact with a file. Please ensure the
> > > > >> package phase is run before the assembly is generated.
> > > > >>
> > > > >> This is weird because all the dependencies are built installed and
> > > ready
> > > > >> to
> > > > >> use.
> > > > >>
> > > > >> Thanks.
> > > > >>
> > > > >> On 11/11/09, Anders Hammar <anders@...> wrote:
> > > > >> > You should bind the assembly plugin to an appropriate phase
> (such
> > as
> > > > >> > 'package'). The, you only need to run
> > > > >> > mvn install
> > > > >> >
> > > > >> > /Anders
> > > > >> >
> > > > >> > On Tue, Nov 10, 2009 at 22:33, Stephanie Johnson
> > > > >> > <jstephanie11@...>wrote:
> > > > >> >
> > > > >> >> All,
> > > > >> >>
> > > > >> >> I am using Maven 2.0.9 to build a multi module project. I have
> > > > defined
> > > > >> the
> > > > >> >> assembly plugin in my parent pom. I can get my assemblies built
> > > using
> > > > >> >>
> > > > >> >> mvn install assembly:assemly
> > > > >> >>
> > > > >> >> This command runs the tests twice, once during install phase
> and
> > > > >> >> another
> > > > >> >> during assembly. I tried assembly:single but it throws an
> error.
> > > Any
> > > > >> help
> > > > >> >> to
> > > > >> >> fix get my assemblies built without running the tests twice is
> > much
> > > > >> >> appreciated.
> > > > >> >>
> > > > >> >> Thanks.
> > > > >> >>
> > > > >> >
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: users-unsubscribe@...
> > > > >> For additional commands, e-mail: users-help@...
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@...
> > > > For additional commands, e-mail: users-help@...
> > > >
> > >
> >
>

From forum: Maven - Users

Re: Re: IDE can not recognize the web module

2009-11-13T19:59:56Z

2009/11/13 Fred Bricon <fbricon@...>

Have you installed the M2E / WTP integration plugin? It's necessary to add the Web facet to your project (among other things).

Thank you very much !!!!

I install the m2e/wtp plugin,and it works.

2009/11/13 maven apache <apachemaven0@...>

2009/11/13 maven apache <apachemaven0@...>

HI:
I have create a web module use m2eclipse by the maven-plugin-webapp archetype.
However I found that I can not debug it .
Since there is no "debug on server " menu when I right click the project.

And I can not change it to a dynamic web project modify the "project facets",since there is no "project facets" item, in the properties of this project.

So I wonder how to debug my web module?

I am using Eclipse EE 3.5 and the m2eclipse is 0.9.8

Nobody？

From forum: Maven Eclipse - User

Re: [VOTE] Release Apache Maven 3.0-alpha-4

2009-11-13T19:47:01Z

I was waiting until alpha-3 was out to merge in the MNG-3004 branch.
MNG-3004 passes all ITs, including a few new ITs of the experimental
multithreaded mode.

Can we recut alpha-4 with MNG-3004 in it?

-Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Maven Developers

properties in settings.xml

2009-11-13T19:43:48Z

Hello,

I have a project which uses nsis to create an installer, but NSIS
isn't available on all of the platforms which I build the project, and
I'd like it to skip making the NSIS when the makensis isn't available.
I'd like to make the path to NSIS be configurable in the ~/.m2/
settings.xml, so I add it to a "default" profile which I created
having a bunch of other properties:

<profiles>
<profile>
<id>default</id>
<properties>
<database.driverClassName>org.postgresql.Driver</
database.driverClassName>
<database.url>jdbc:postgresql://localhost/test</database.url>
<database.user>user</database.user>
<database.password>password</database.password>
<cargo.tomcat.manager.url>http://localhost:8081/manager</
cargo.tomcat.manager.url>
<cargo.remote.username>manager</cargo.remote.username>
<cargo.remote.password>password</cargo.remote.password>
<customer.webapp.context>/</customer.webapp.context>
<client.webapp.context>/client</client.webapp.context>
<nsis.path>/usr/local/nsis/nsis-2.45/bin/makensis</nsis.path>

</properties>
</profile>
</profiles>

So, I have a nsis.path defined in there. However, I am trying to
activate the profile in my pom and neither way works. I've tried to just
activate the profile in the pom based on presence of nsis.path
variable and that doesn't work. And then I've also tried to do:

<file><exists>${nsis.path}</exists></file>

and that doesn't work either.

How can I accomplish this? I could activate it manually with -P, but
I'd rather just have everything in the settings.xml file since I need
to visit that to setup the environment anyways.

thanks!

-jr

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Maven - Users

repo doesn't contain its dependencies?

2009-11-13T17:59:35Z

I noticed that the java.net maven2 repo
contains this jar:

<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
<version>1.1.4</version>
</dependency>

however, it doesn't contain several of the dependencies of said
jar--like glassfish embedded, etc.

Anybody know if this is expected?
Thanks!
-r

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Maven - Users

Commented: (MECLIPSE-531) eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking

2009-11-13T16:40:55Z

[ http://jira.codehaus.org/browse/MECLIPSE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198287#action_198287 ]

Adrian Wilkins commented on MECLIPSE-531:
-----------------------------------------

I think this is a problem with the mismatch between the way that Maven uses version numbers and everything else does.

Maven uses a -SNAPSHOT or similar suffix to indicate versions earlier than that in the main version number. Everything else seems to use this to indicate later versions (Eclipse being one of these things).

So Eclipse is using the qualifier (fourth segment) to mark versions AFTER the version number incremented, Maven is taking the fourth segment to be versions BEFORE the version number incremented.

From "DefaultArtifactVersion.java"

// otherVersion has a qualifier but we don't, we're newer

The fourth segment in Eclipse version numbers doesn't correspond to the same thing as Mavens "qualifier" even if it's called the same thing. It's more like "build number" (which is currently required to be an integer in Maven, so that would have to change to support this).

Stripping qualifiers is probably the only short-term fix. If the modules in question are following the version numbering policy there should be no API breaks ; the downside is that your repository may end up holding older versions of some components. You should probably run eclipse:to-maven after each Eclipse update, into a central repository if there is more than one person working on the project.

I think a real fix for this would be to permit arbitrary strings in the "build number" field on DefaultArtifactVersion class, although this will complicate it very slightly ; then you'd have to fix the eclipse:to-maven mojo to put eclipse-qualifier in the build number field where it should be, instead of the maven-qualifier field where it stops things working.

I'm going to delete my "eclipse" repository hierarchy and run it again with stripped qualifiers now. Bah.

> eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking
> -------------------------------------------------------------------------------------
>
> Key: MECLIPSE-531
> URL: http://jira.codehaus.org/browse/MECLIPSE-531
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Affects Versions: 2.5.1
> Environment: Windows XP SP3, Maven 2.0.9, Java 1.6.0.11
> Reporter: Costin Caraivan
>
> If you use eclipse:to-maven, the resulting artifacts have poms containing versions like these, for dependencies: [3.2.0,4.0.0).
> End result =>
> Couldn't find a version in [3.2.0-v3232o] to match range [3.2.0,4.0.0)
> I believe that to-maven needs an option like make-artifacts, to resolveVersionRanges, because stripping qualifiers means that we lose information (Eclipse 3.4 has some 3.2.0 plugins for example, but with a different qualifier than the original 3.2 Eclipse plugins).
> Or the version ranges need to be fixed, something like this: [3.2.0-, 4.0.0-).
> Thank you.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Maven - Issues

Re: mvn deploy to hosted repo: 5 sec to upload, 3 min to process?

2009-11-13T16:32:55Z

We're doing some digging into this. The current plan is to begin staging 1.4.1 early next week. I'll let you know what we find.

--Brian (mobile)

On Nov 13, 2009, at 12:31 PM, "Hayes, Peter" <Peter.Hayes@...> wrote:

We see the same issues when uploading 50mb war files. We generally see total times of 3 - 4 minutes. In our case, the entire time is spent writing to the tmp war file. The move / rename to the actual war file seems instantaneous and maven cli becomes responsive immediately afterwards. An ftp of the same file among the same servers take 15 seconds.

From: t.cservenak@... [mailto:t.cservenak@...] On Behalf Of Tamás Cservenák
Sent: Tuesday, November 10, 2009 12:33 PM
To: nexus-user@...
Subject: Re: [nexus-user] mvn deploy to hosted repo: 5 sec to upload, 3 min to process?

@03:39: the WAR upload begins (Jetty got REQUEST) -- "from somewhere" is the HTTP Request body of your Maven (jetty log states that it just got a request)

@04:37: the WAR upload ends (Jetty sends back RESPONSE 201 "created") -- file should be written to disk completely

That's 58 seconds for the WAR. The other "gross" time you see is all the other "maven nitty-bitty" stuff, like sha1+md5, metadata and POM deployment.

At the log beginning, there is some request ending with a 401 (probably Maven tries to act without authenticating), then there is a pause of appx a minute (02:43 - 03:39) where Nexus not having any incoming request. Probably Maven is working locally.

Hope helps,

~t~

On Tue, Nov 10, 2009 at 6:18 PM, dukehoops <nikita.tovstoles@...> wrote:

Not sure I can confirm anything - I am a Nexus newbie - but here's a Nexus
debug file covering a single mvn deploy-triggered upload of a 42mb WAR
artifact (same as described in my initial post). Things to note:
-upload kicks off at 10:02:43
-on the client side, mvn deploy's upload indicator reaches 100% about 3
seconds later
-on server side EOF takes place at 10:03:39 - (about a minute later)
-- right above, the last two lines of 02:43 complain about 'perms/roles' but
the upload seems to proceed successfully anyway (What's that about? the user
in question has 'deployment' role for all repos)
- then, from 03:39 to 04:37 (another minute) something's copying the war
from somewhere to repo storage dir. Where is
"/com/kijiji/c4war/4.0.e000-ntovstoles/c4war-4.0.e000-ntovstoles.war"
relative to nexus home?
- we're done at 04:39

Log attached:
http://old.nabble.com/file/p26287334/nexus-debug.log nexus-debug.log

Rich Seddon wrote:
>
> FWIW, I've seen a delay with large artifacts as well.
>
> In my observation the files are actually done uploading when the progress
> indicator reaches it's maximum, if you look in the Nexus storage directory
> you will see them.
>
> What seems to be happening is that the checksum calculation (md5 and sha1)
> takes a long time for large files, and Maven doesn't proceed until this
> has finished.
>
> Perhaps someone can confirm?
>
> Rich
>
>
> On Nov 10, 2009, at 8:37 AM, dukehoops wrote:
>
>>
>> Client:
>>
>> win server 2003 x64 SP2; 3g Xeon, 8gb ram, SCSI
>>
>> D:\Views\main\v3classifieds\c4war>java -version
>> java version "1.5.0"
>> Java(TM) 2 Runtime Environment, Standard Edition (build
>> pwi32dev-20080710a
>> (SR8))
>> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32
>> j9vmwi3223-20080710 (JIT enabled)
>> J9VM - 20080625_20583_lHdSMr
>> JIT - 20080620_1845_r8
>> GC - 200806_19)
>> JCL - 20080710
>>
>> SERVER:
>> 4 2xCore Xeon, RHEL 2.6.9-78.0.8.ELsmp, not sure what kind of disk (but
>> it's
>> big ;-) Here's how nexus's running:
>>
>> [root@sjd-pdvas-005 ~]# ps aux | grep nexus
>> nexus 11932 0.0 0.0 11916 620 ? Sl Aug26 0:00
>> /opt/nexus/nexus-webapp-1.3.6/bin/jsw/linux-x86-32/./wrapper
>> /opt/nexus/nexus-webapp-1.3.6/bin/jsw/linux-x86-32/../../../conf/wrapper.conf
>> wrapper.syslog.ident=nexus-webapp
>> wrapper.pidfile=/opt/nexus/nexus-webapp-1.3.6/bin/jsw/linux-x86-32/./nexus-webapp.pid
>> wrapper.daemonize=TRUE
>> nexus 11944 0.0 2.1 612628 175648 ? Sl Aug26 19:05
>> /opt/c4/java/bin/java -Dbasedir=../../..
>> -Djava.io.tmpdir=../../../runtime/tmp -Dsun.net.inetaddr.ttl=3600
>> -Djava.library.path=./lib -classpath
>> ../../../lib/plexus-platform-jsw-1.6.6.jar:../../../conf/
>> -Dwrapper.key=QpVAMS4usm08Tv4G -Dwrapper.port=32000
>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
>> -Dwrapper.pid=11932 -Dwrapper.version=3.2.3
>> -Dwrapper.native_library=wrapper
>> -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
>> org.codehaus.plexus.classworlds.launcher.Launcher
>>
>> ...using this VM:
>>
>> java version "1.5.0"
>> Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20080315
>> (SR7))
>> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32
>> j9vmxi3223-20080315
>> (JIT enabled)
>> J9VM - 20080314_17962_lHdSMr
>> JIT - 20080130_0718ifx2_r8
>> GC - 200802_08)
>> JCL - 20080314
>>
>>
>>
>> Brian Fox wrote:
>>>
>>> On Tue, Nov 10, 2009 at 11:24 AM, dukehoops <nikita.tovstoles@...>
>>> wrote:
>>>>
>>>> Are you saying mvn's upload progress indicator may not reflect actual
>>>> network
>>>> traffic (by 60x)?
>>>
>>> Yes, that's my suspicion. What OS is your server and client on? We
>>> have seen that some tweaks to the jetty config can improve performance
>>> if the server is on Windows.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>>> For additional commands, e-mail: nexus-user-help@...
>>>
>>>
>>>
>>
>>
>> -----
>> ----------------
>> Nikita Tovstoles
>> vside.com
>> ----------------
>>
>> --
>> View this message in context:
>> http://old.nabble.com/mvn-deploy-to-hosted-repo%3A-5-sec-to-upload%2C-3-min-to-process--tp26274731p26286648.html
>> Sent from the Nexus Maven Repository Manager Users List mailing list
>> archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>> For additional commands, e-mail: nexus-user-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>
>

-----
----------------
Nikita Tovstoles
vside.com
----------------

--

View this message in context: http://old.nabble.com/mvn-deploy-to-hosted-repo%3A-5-sec-to-upload%2C-3-min-to-process--tp26274731p26287334.html

Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

From forum: Nexus Maven Repository Manager Users List

svn commit: r836075 - in /maven/mercury/trunk: mercury-it/pom.xml pom.xml

2009-11-13T16:18:18Z

Author: olamy
Date: Sat Nov 14 00:18:18 2009
New Revision: 836075

URL: http://svn.apache.org/viewvc?rev=836075&view=rev
Log:
upgrade to last plexus version

Modified:
maven/mercury/trunk/mercury-it/pom.xml
maven/mercury/trunk/pom.xml

Modified: maven/mercury/trunk/mercury-it/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-it/pom.xml?rev=836075&r1=836074&r2=836075&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-it/pom.xml (original)
+++ maven/mercury/trunk/mercury-it/pom.xml Sat Nov 14 00:18:18 2009
@@ -36,10 +36,6 @@
</dependencyManagement>

<properties>
-
- <maven.version>3.0-SNAPSHOT</maven.version>
<spice.model.builder.version>1.5</spice.model.builder.version>
<plexus.webdav.version>1.0</plexus.webdav.version>
</properties>
@@ -169,9 +165,9 @@
</dependency>

<dependency>
- <groupId>commons-cli</groupId>
- <artifactId>commons-cli</artifactId>
- <scope>test</scope>
+ <groupId>commons-cli</groupId>
+ <artifactId>commons-cli</artifactId>
+ <scope>test</scope>
</dependency>

</dependencies>

Modified: maven/mercury/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/pom.xml?rev=836075&r1=836074&r2=836075&view=diff
==============================================================================
--- maven/mercury/trunk/pom.xml (original)
+++ maven/mercury/trunk/pom.xml Sat Nov 14 00:18:18 2009
@@ -63,9 +63,9 @@
<classworlds.version>1.3</classworlds.version>

<plexus.appbooter.version>1.4</plexus.appbooter.version>
- <plexus.container.version>1.0-beta-3.0.6</plexus.container.version>
- <plexus.component.annotations.version>1.0-beta-3.0.6</plexus.component.annotations.version>
- <plexus.component.metadata.version>1.0-beta-3.0.6</plexus.component.metadata.version>
+ <plexus.container.version>1.5.1</plexus.container.version>
+ <plexus.component.annotations.version>1.5.1</plexus.component.annotations.version>
+ <plexus.component.metadata.version>1.5.1</plexus.component.metadata.version>
<plexus.utils.version>1.5.5</plexus.utils.version>
<plexus.lang.version>1.1</plexus.lang.version>

From forum: Maven - Commits

svn commit: r836070 - /maven/mercury/trunk/pom.xml

2009-11-13T16:09:17Z

Author: olamy
Date: Sat Nov 14 00:09:15 2009
New Revision: 836070

URL: http://svn.apache.org/viewvc?rev=836070&view=rev
Log:
upgrade plugins version :
- release plugin
- modello plugin

Modified:
maven/mercury/trunk/pom.xml

Modified: maven/mercury/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/pom.xml?rev=836070&r1=836069&r2=836070&view=diff
==============================================================================
--- maven/mercury/trunk/pom.xml (original)
+++ maven/mercury/trunk/pom.xml Sat Nov 14 00:09:15 2009
@@ -377,8 +377,9 @@

<plugins>
<plugin>
+ <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
- <version>2.0-beta-8</version>
+ <version>2.0-beta-9</version>
<configuration>
<tagBase>https://svn.apache.org/repos/asf/maven/mercury/tags</tagBase>
<autoVersionSubmodules>true</autoVersionSubmodules>
@@ -402,7 +403,7 @@
<plugin>
<groupId>org.codehaus.modello</groupId>
<artifactId>modello-maven-plugin</artifactId>
- <version>1.0.1</version>
+ <version>1.1</version>
<configuration>
<useJava5>true</useJava5>
</configuration>
@@ -419,11 +420,6 @@

<plugin>
<groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-release-plugin</artifactId>
- </plugin>
-
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>

From forum: Maven - Commits

svn commit: r836066 - /maven/mercury/trunk/pom.xml

2009-11-13T16:04:19Z

Author: olamy
Date: Sat Nov 14 00:04:18 2009
New Revision: 836066

URL: http://svn.apache.org/viewvc?rev=836066&view=rev
Log:
use pluginManagement section

Modified:
maven/mercury/trunk/pom.xml

Modified: maven/mercury/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/pom.xml?rev=836066&r1=836065&r2=836066&view=diff
==============================================================================
--- maven/mercury/trunk/pom.xml (original)
+++ maven/mercury/trunk/pom.xml Sat Nov 14 00:04:18 2009
@@ -407,6 +407,11 @@
<useJava5>true</useJava5>
</configuration>
</plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>2.4.1</version>
+ </plugin>
</plugins>
</pluginManagement>

@@ -438,18 +443,13 @@
<target>1.5</target>
</configuration>
</plugin>
-
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-resources-plugin</artifactId>
- <version>2.4.1</version>
- </plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
</plugin>
<plugin>
+ <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.0-alpha-4</version>
<executions>

From forum: Maven - Commits

svn commit: r836065 - /maven/mercury/trunk/pom.xml

2009-11-13T16:02:11Z

Author: olamy
Date: Sat Nov 14 00:02:11 2009
New Revision: 836065

URL: http://svn.apache.org/viewvc?rev=836065&view=rev
Log:
add a m2e profile to use incremental build.

Modified:
maven/mercury/trunk/pom.xml

Modified: maven/mercury/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/pom.xml?rev=836065&r1=836064&r2=836065&view=diff
==============================================================================
--- maven/mercury/trunk/pom.xml (original)
+++ maven/mercury/trunk/pom.xml Sat Nov 14 00:02:11 2009
@@ -438,6 +438,12 @@
<target>1.5</target>
</configuration>
</plugin>
+
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>2.4.1</version>
+ </plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -601,6 +607,40 @@
</plugins>
</reporting>
</profile>
+
+ <profile>
+ <id>m2e</id>
+ <properties>
+ <m2BuildDirectory>target</m2BuildDirectory>
+ </properties>
+ <activation>
+ <property>
+ <name>m2e.version</name>
+ </property>
+ </activation>
+ <build>
+ <directory>${m2BuildDirectory}</directory>
+ <plugins>
+ <plugin>
+ <groupId>org.maven.ide.eclipse</groupId>
+ <artifactId>lifecycle-mapping</artifactId>
+ <version>0.9.9-SNAPSHOT</version>
+ <configuration>
+ <mappingId>customizable</mappingId>
+ <configurators>
+ <configurator id="org.maven.ide.eclipse.jdt.javaConfigurator" />
+ <configurator id="org.maven.ide.eclipse.modello.modelloConfigurator" />
+ <configurator id="org.maven.ide.eclipse.plexus.annotations.plexusConfigurator" />
+ </configurators>
+ <mojoExecutions>
+ <mojoExecution>org.apache.maven.plugins:maven-resources-plugin::</mojoExecution>
+ </mojoExecutions>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+

<profile>
<id>run-its</id>

From forum: Maven - Commits

svn commit: r836062 - in /maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus: DefaultPlexusMercury.java PlexusMercury.java PlexusMercuryException.java

2009-11-13T15:49:14Z

Author: olamy
Date: Fri Nov 13 23:49:13 2009
New Revision: 836062

URL: http://svn.apache.org/viewvc?rev=836062&view=rev
Log:
apply some formatting

Modified:
maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/DefaultPlexusMercury.java
maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercury.java
maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercuryException.java

Modified: maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/DefaultPlexusMercury.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/DefaultPlexusMercury.java?rev=836062&r1=836061&r2=836062&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/DefaultPlexusMercury.java (original)
+++ maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/DefaultPlexusMercury.java Fri Nov 13 23:49:13 2009
@@ -96,11 +96,13 @@
DependencyProcessor dp = null;

if ( _dependencyProcessors != null )
+ {
dp = _dependencyProcessors.get( hint );
-
+ }
if ( dp == null )
+ {
throw new RepositoryException( LANG.getMessage( "no.dep.processor.injected", hint ) );
-
+ }
return dp;
}

@@ -201,8 +203,9 @@
throws RepositoryException
{
if ( repo == null )
+ {
throw new RepositoryException( LANG.getMessage( "null.repo" ) );
-
+ }
RepositoryWriter wr = repo.getWriter();

wr.writeArtifacts( artifacts );
@@ -215,27 +218,36 @@
throws RepositoryException
{
if ( Util.isEmpty( repos ) )
+ {
throw new RepositoryException( LANG.getMessage( "null.repo" ) );
-
+ }
VirtualRepositoryReader vr = new VirtualRepositoryReader( repos );

ArtifactResults ar = vr.readArtifacts( artifacts );

if ( ar == null || !ar.hasResults() )
+ {
return null;
-
+ }
+
if ( ar.hasExceptions() && LOG.isWarnEnabled() )
+ {
LOG.info( ar.getExceptions().toString() );
-
+ }
+
if ( !ar.hasResults() )
+ {
return null;
-
+ }
+
Map<ArtifactMetadata, List<Artifact>> am = ar.getResults();

List<Artifact> al = new ArrayList<Artifact>();
for ( Map.Entry<ArtifactMetadata, List<Artifact>> e : am.entrySet() )
+ {
al.addAll( e.getValue() );
-
+ }
+
return al;

}
@@ -285,8 +297,10 @@
throws RepositoryException
{
if ( Util.isEmpty( artifacts ) || artifacts.isEmpty() )
+ {
throw new IllegalArgumentException( LANG.getMessage( "no.artifacts" ) );
-
+ }
+
try
{
DependencyBuilder depBuilder =
@@ -319,8 +333,10 @@
throws RepositoryException
{
if ( Util.isEmpty( artifacts ) || artifacts.isEmpty() )
+ {
throw new IllegalArgumentException( LANG.getMessage( "no.artifacts" ) );
-
+ }
+
try
{
DependencyBuilder depBuilder =
@@ -375,11 +391,15 @@
MetadataResults res = vr.readVersions( q );

if ( res == null )
+ {
return null;
-
+ }
+
if ( res.hasExceptions() && LOG.isWarnEnabled() )
+ {
LOG.warn( res.getExceptions().toString() );
-
+ }
+
return res.getResult( query );
}

@@ -400,13 +420,15 @@
repos.add( lr );

if ( nRemote > 0 )
+ {
for ( String url : urls )
{
RemoteRepositoryM2 rr = new RemoteRepositoryM2( url, dp );

repos.add( rr );
}
-
+ }
+
return repos;

}

Modified: maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercury.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercury.java?rev=836062&r1=836061&r2=836062&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercury.java (original)
+++ maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercury.java Fri Nov 13 23:49:13 2009
@@ -54,7 +54,7 @@
* @return the dependency processor
* @throws RepositoryException
*/
- public DependencyProcessor findDependencyProcessor()
+ DependencyProcessor findDependencyProcessor()
throws RepositoryException;

/**
@@ -64,7 +64,7 @@
* @return the dependency processor
* @throws RepositoryException
*/
- public DependencyProcessor findDependencyProcessor( String hint )
+ DependencyProcessor findDependencyProcessor( String hint )
throws RepositoryException;

/**
@@ -76,7 +76,7 @@
* @return pgp verifier factory to be sent to Repository
* @throws PlexusMercuryException
*/
- public PgpStreamVerifierFactory createPgpReaderFactory( boolean lenient, boolean sufficient, InputStream pubRing )
+ PgpStreamVerifierFactory createPgpReaderFactory( boolean lenient, boolean sufficient, InputStream pubRing )
throws StreamVerifierException;

/**
@@ -90,7 +90,7 @@
* @return pgp verifier factory to be sent to Repository
* @throws PlexusMercuryException
*/
- public PgpStreamVerifierFactory createPgpWriterFactory( boolean lenient, boolean sufficient, InputStream secRing,
+ PgpStreamVerifierFactory createPgpWriterFactory( boolean lenient, boolean sufficient, InputStream secRing,
String keyId, String keyPass )
throws StreamVerifierException;

@@ -111,7 +111,7 @@
* @return repository instance
* @throws PlexusMercuryException
*/
- public RemoteRepositoryM2 constructRemoteRepositoryM2( String id, URL serverUrl, String serverUser,
+ RemoteRepositoryM2 constructRemoteRepositoryM2( String id, URL serverUrl, String serverUser,
String serverPass, URL proxyUrl, String proxyUser,
String proxyPass,
Set<StreamObserverFactory> readerStreamObservers,
@@ -132,7 +132,7 @@
* @return repository instance
* @throws PlexusMercuryException
*/
- public LocalRepositoryM2 constructLocalRepositoryM2( String id, File rootDir,
+ LocalRepositoryM2 constructLocalRepositoryM2( String id, File rootDir,
Set<StreamObserverFactory> readerStreamObservers,
Set<StreamVerifierFactory> readerStreamVerifiers,
Set<StreamObserverFactory> writerStreamObservers,
@@ -147,7 +147,7 @@
* @return repository list
* @throws PlexusMercuryException
*/
- public List<Repository> constructRepositories( String localDir, String... urls )
+ List<Repository> constructRepositories( String localDir, String... urls )
throws RepositoryException;

/**
@@ -158,10 +158,10 @@
* @return
* @throws PlexusMercuryException
*/
- public void write( Repository repo, Artifact... artifacts )
+ void write( Repository repo, Artifact... artifacts )
throws RepositoryException;

- public void write( Repository repo, Collection<Artifact> artifacts )
+ void write( Repository repo, Collection<Artifact> artifacts )
throws RepositoryException;

/**
@@ -172,10 +172,10 @@
* @return
* @throws PlexusMercuryException
*/
- public List<Artifact> read( List<Repository> repo, List<? extends ArtifactMetadata> artifacts )
+ List<Artifact> read( List<Repository> repo, List<? extends ArtifactMetadata> artifacts )
throws RepositoryException;

- public List<Artifact> read( List<Repository> repo, ArtifactMetadata... artifacts )
+ List<Artifact> read( List<Repository> repo, ArtifactMetadata... artifacts )
throws RepositoryException;

/**
@@ -189,27 +189,27 @@
* @return
* @throws PlexusMercuryException
*/
- public List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope,
+ List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope,
ArtifactQueryList artifacts, ArtifactInclusionList inclusions,
ArtifactExclusionList exclusions )
throws RepositoryException;

- public List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope,
+ List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope,
ArtifactQueryList artifacts, ArtifactInclusionList inclusions,
ArtifactExclusionList exclusions, Map<String, ?> config )
throws RepositoryException;

- public MetadataTreeNode resolveAsTree( List<Repository> repos, ArtifactScopeEnum scope,
+ MetadataTreeNode resolveAsTree( List<Repository> repos, ArtifactScopeEnum scope,
ArtifactQueryList artifacts, ArtifactInclusionList inclusions,
ArtifactExclusionList exclusions )
throws RepositoryException;

- public MetadataTreeNode resolveAsTree( List<Repository> repos, ArtifactScopeEnum scope,
+ MetadataTreeNode resolveAsTree( List<Repository> repos, ArtifactScopeEnum scope,
ArtifactQueryList artifacts, ArtifactInclusionList inclusions,
ArtifactExclusionList exclusions, Map<String, ?> config )
throws RepositoryException;

- public List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope, ArtifactMetadata metadata )
+ List<ArtifactMetadata> resolve( List<Repository> repos, ArtifactScopeEnum scope, ArtifactMetadata metadata )
throws RepositoryException;

/**
@@ -220,6 +220,6 @@
* @return list of found version metadatas
* @throws PlexusMercuryException
*/
- public List<ArtifactMetadata> readVersions( List<Repository> repos, ArtifactMetadata query )
+ List<ArtifactMetadata> readVersions( List<Repository> repos, ArtifactMetadata query )
throws RepositoryException;
}

Modified: maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercuryException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercuryException.java?rev=836062&r1=836061&r2=836062&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercuryException.java (original)
+++ maven/mercury/trunk/mercury-plexus/src/main/java/org/apache/maven/mercury/plexus/PlexusMercuryException.java Fri Nov 13 23:49:13 2009
@@ -24,6 +24,7 @@

public PlexusMercuryException()
{
+ // nothing
}

public PlexusMercuryException( String message )

From forum: Maven - Commits

RE: Problem in creating own archetype

2009-11-13T15:49:10Z

I should mention that compile and install of archetype works fine, I am
encountering all these issues when I am trying to create the archetype

-----Original Message-----
From: Qureshi,Shahzad [Ontario] [mailto:Shahzad.Qureshi@...]
Sent: Friday, November 13, 2009 6:46 PM
To: users@...
Subject: Problem in creating own archetype

Hi all,

I am trying to convince my group here to start using Maven instead of
Ant. I am preparing a demonstration for them and in the process, I am
trying to create my own archetype. I've done it before but this time I
am stuck at something which I've no idea how to solve.

I want the project directory structure to be

- bin
-- file1
-- file2.sh
-- file3.sh
- src
-- main
-- java
-- file.java
+ site
+ test

So I've all that setup in archetype-resources folder and here is my
archetype.xml within META-INF directory

<archetype>

<id>archetype_id</id>
<sources>
<source>src/main/java/App.java</source>
</sources>
<testSources>
<source>src/test/java/AppTest.java</source>
</testSources>
<resources>
<resource>bin/file1</resource>
<resource>bin/file2.sh</resource>
<resource>bin/file3.sh</resource>
</resources>
</archetype>

The amount of problems I am encountering with something simple as this,
I've a feeling that this resources folder is supposed to do something
other then what I am trying to do.

Q1- How do I include the bin folder where I want it?

Main problem I am encountering is I haven't been able to figure out how
to include the entire directory and its files without specifying each
file the way I've shown above and ** doesn't work and neither does
specifying a directory and include tag

ANOTHER weird problem is that when Maven encounters that file2.sh, it
for some reason tries to open it and parse it because I get an exception
like this.... Parser Eception:
archetype-resources/bin/file2.sh:org.apache.velocity.runtime.parser.Pars
eException: Encountered .....

Q2- Why is Maven trying to parse my shell script?

I would appreciate any help you can provide, if I am unable to prove to
my group how useful Maven is (this is the only snag left), I am afraid
we'll keep using ANT

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Maven - Users

Commented: (MNG-4443) gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]

2009-11-13T15:46:55Z

[ http://jira.codehaus.org/browse/MNG-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198280#action_198280 ]

Olivier Lamy commented on MNG-4443:
-----------------------------------

as I can see there are some gwt compilation issue. As gwt-2.0.0-ms2 is not in central repo it's difficult to test your project. Does it works with ms1 ?

> gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]
> ----------------------------------------------------------------
>
> Key: MNG-4443
> URL: http://jira.codehaus.org/browse/MNG-4443
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-3
> Environment: Mac OS X 10.5.8, Windows XP SP2
> Reporter: Tiago Fernandez
> Attachments: build.log, pom.xml
>
>
> I am used to build my GWT app (http://github.com/tiagofernandez/bazooka) with Maven 2.x without any problem, but when I try a clean packaging with Maven 3.0-alpha-3 I get the following error:
> [ERROR] GWTCompiler failed -> [Help 1]
> org.apache.maven.plugin.MojoExecutionException: GWTCompiler failed
> at org.codehaus.mojo.gwt.CompileMojo.compile(CompileMojo.java:136)
> at org.codehaus.mojo.gwt.CompileMojo.execute(CompileMojo.java:99)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:239)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:102)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:421)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:156)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> [ERROR]
> I have attached the build.log with debug logs and exception traces and the pom.xml I'm using.
> If you need more details, feel free to ask me. Thanks.

From forum: Maven - Issues

Closed: (MNG-4443) gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]

2009-11-13T15:46:55Z

[ http://jira.codehaus.org/browse/MNG-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4443.
----------------------------------

Resolution: Not A Bug
Assignee: Benjamin Bentmann

I managed to reproduce the compilation failure when using gwt-maven-plugin:1.0 with both Maven 2.2.1 and Maven 3.0-alpha-3. The project builds fine as soon as the gwt-maven-plugin is locked down to version 1.1, again with both Maven 2.2.1 and 3.0-alpha-3. So it's just a matter of specifying the correct plugin version.

The difference between Maven 2 and 3 in case of a missing plugin version results from the current metadata for gwt-maven-plugin:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.0</version>
<versioning>
<latest>1.1</latest>
<release>1.0</release>
<versions>
<version>1.0</version>
<version>1.1</version>
</versions>
<lastUpdated>20090618131729</lastUpdated>
</versioning>
</metadata>
{code}
which lists latest=1.1 but release=1.0. Maven 3 intentionally prefers "release" over "latest". Given the version 1.1 of the plugin has neither sources nor javadoc, I guess the release manager did not use the Maven Release Plugin, thereby producing a bad plugin release.

> gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]
> ----------------------------------------------------------------
>
> Key: MNG-4443
> URL: http://jira.codehaus.org/browse/MNG-4443
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-3
> Environment: Mac OS X 10.5.8, Windows XP SP2
> Reporter: Tiago Fernandez
> Assignee: Benjamin Bentmann
> Attachments: build.log, pom.xml
>
>
> I am used to build my GWT app (http://github.com/tiagofernandez/bazooka) with Maven 2.x without any problem, but when I try a clean packaging with Maven 3.0-alpha-3 I get the following error:
> [ERROR] GWTCompiler failed -> [Help 1]
> org.apache.maven.plugin.MojoExecutionException: GWTCompiler failed
> at org.codehaus.mojo.gwt.CompileMojo.compile(CompileMojo.java:136)
> at org.codehaus.mojo.gwt.CompileMojo.execute(CompileMojo.java:99)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:239)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:102)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:421)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:156)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> [ERROR]
> I have attached the build.log with debug logs and exception traces and the pom.xml I'm using.
> If you need more details, feel free to ask me. Thanks.

From forum: Maven - Issues

Problem in creating own archetype

2009-11-13T15:46:12Z

Hi all,

I am trying to convince my group here to start using Maven instead of
Ant. I am preparing a demonstration for them and in the process, I am
trying to create my own archetype. I've done it before but this time I
am stuck at something which I've no idea how to solve.

I want the project directory structure to be

- bin
-- file1
-- file2.sh
-- file3.sh
- src
-- main
-- java
-- file.java
+ site
+ test

So I've all that setup in archetype-resources folder and here is my
archetype.xml within META-INF directory

<archetype>

<id>archetype_id</id>
<sources>
<source>src/main/java/App.java</source>
</sources>
<testSources>
<source>src/test/java/AppTest.java</source>
</testSources>
<resources>
<resource>bin/file1</resource>
<resource>bin/file2.sh</resource>
<resource>bin/file3.sh</resource>
</resources>
</archetype>

The amount of problems I am encountering with something simple as this,
I've a feeling that this resources folder is supposed to do something
other then what I am trying to do.

Q1- How do I include the bin folder where I want it?

Main problem I am encountering is I haven't been able to figure out how
to include the entire directory and its files without specifying each
file the way I've shown above and ** doesn't work and neither does
specifying a directory and include tag

ANOTHER weird problem is that when Maven encounters that file2.sh, it
for some reason tries to open it and parse it because I get an exception
like this.... Parser Eception:
archetype-resources/bin/file2.sh:org.apache.velocity.runtime.parser.Pars
eException: Encountered .....

Q2- Why is Maven trying to parse my shell script?

I would appreciate any help you can provide, if I am unable to prove to
my group how useful Maven is (this is the only snag left), I am afraid
we'll keep using ANT

From forum: Maven - Users

svn commit: r836061 - in /maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury: artifact/ artifact/api/ artifact/version/ builder/api/

2009-11-13T15:46:06Z

Author: olamy
Date: Fri Nov 13 23:46:06 2009
New Revision: 836061

URL: http://svn.apache.org/viewvc?rev=836061&view=rev
Log:
apply some formatting

Modified:
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/ConflictException.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/QualityRange.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ArtifactListProcessorException.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationException.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationUtil.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/AttributeQueryException.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/DefaultArtifactVersion.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/VersionRange.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/DependencyProcessorException.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReader.java
maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReaderException.java

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/ConflictException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/ConflictException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/ConflictException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/ConflictException.java Fri Nov 13 23:46:06 2009
@@ -31,7 +31,7 @@
*/
public ConflictException()
{
- // TODO Auto-generated constructor stub
+ // nothing
}

/**
@@ -40,7 +40,6 @@
public ConflictException( String message )
{
super( message );
- // TODO Auto-generated constructor stub
}

/**
@@ -49,7 +48,6 @@
public ConflictException( Throwable cause )
{
super( cause );
- // TODO Auto-generated constructor stub
}

/**
@@ -59,7 +57,6 @@
public ConflictException( String message, Throwable cause )
{
super( message, cause );
- // TODO Auto-generated constructor stub
}

}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/QualityRange.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/QualityRange.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/QualityRange.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/QualityRange.java Fri Nov 13 23:46:06 2009
@@ -70,12 +70,17 @@
public static QualityRange create( boolean releases, boolean snapshots )
{
if ( releases && snapshots )
+ {
return ALL;
+ }
else if ( releases )
+ {
return new QualityRange( Quality.ALPHA_QUALITY, true, Quality.RELEASE_QUALITY, true );
+ }
else if ( snapshots )
+ {
return new QualityRange( Quality.SNAPSHOT_QUALITY, true, Quality.SNAPSHOT_TS_QUALITY, true );
-
+ }
throw new IllegalArgumentException( LANG.getMessage( "quality.no.sn.no.rel" ) );
}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ArtifactListProcessorException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ArtifactListProcessorException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ArtifactListProcessorException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ArtifactListProcessorException.java Fri Nov 13 23:46:06 2009
@@ -31,7 +31,7 @@
*/
public ArtifactListProcessorException()
{
- // TODO Auto-generated constructor stub
+ // nothing
}

/**
@@ -40,7 +40,6 @@
public ArtifactListProcessorException( String message )
{
super( message );
- // TODO Auto-generated constructor stub
}

/**
@@ -49,7 +48,6 @@
public ArtifactListProcessorException( Throwable cause )
{
super( cause );
- // TODO Auto-generated constructor stub
}

/**
@@ -59,7 +57,6 @@
public ArtifactListProcessorException( String message, Throwable cause )
{
super( message, cause );
- // TODO Auto-generated constructor stub
}

}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationException.java Fri Nov 13 23:46:06 2009
@@ -6,6 +6,7 @@

public ConfigurationException()
{
+ // nothing
}

public ConfigurationException( String message )

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationUtil.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationUtil.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationUtil.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/api/ConfigurationUtil.java Fri Nov 13 23:46:06 2009
@@ -31,9 +31,12 @@
throws ConfigurationException
{
if ( impl == null || config == null )
+ {
return;
-
+ }
for ( Map.Entry<String, Object> e : config.entrySet() )
+ {
impl.setOption( e.getKey(), e.getValue() );
+ }
}
}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/AttributeQueryException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/AttributeQueryException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/AttributeQueryException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/AttributeQueryException.java Fri Nov 13 23:46:06 2009
@@ -31,7 +31,7 @@
*/
public AttributeQueryException()
{
- // TODO Auto-generated constructor stub
+ // nothing
}

/**
@@ -40,7 +40,6 @@
public AttributeQueryException( String message )
{
super( message );
- // TODO Auto-generated constructor stub
}

/**
@@ -49,7 +48,6 @@
public AttributeQueryException( Throwable cause )
{
super( cause );
- // TODO Auto-generated constructor stub
}

/**
@@ -59,7 +57,6 @@
public AttributeQueryException( String message, Throwable cause )
{
super( message, cause );
- // TODO Auto-generated constructor stub
}

}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/DefaultArtifactVersion.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/DefaultArtifactVersion.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/DefaultArtifactVersion.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/DefaultArtifactVersion.java Fri Nov 13 23:46:06 2009
@@ -20,7 +20,7 @@
import org.apache.maven.mercury.artifact.Artifact;
import org.apache.maven.mercury.artifact.Quality;

-/*
+/**
* Default implementation of artifact versioning.
*
* @author <a href="mailto:brett@...">Brett Porter</a>

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/VersionRange.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/VersionRange.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/VersionRange.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/artifact/version/VersionRange.java Fri Nov 13 23:46:06 2009
@@ -35,10 +35,10 @@
* @param version to test
* @return
*/
- public boolean includes( String version );
+ boolean includes( String version );

/**
* @return true if the range is good old single version, not a true range
*/
- public boolean isSingleton();
+ boolean isSingleton();
}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/DependencyProcessorException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/DependencyProcessorException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/DependencyProcessorException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/DependencyProcessorException.java Fri Nov 13 23:46:06 2009
@@ -32,6 +32,7 @@
*/
public DependencyProcessorException()
{
+ // nothing
}

/**

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReader.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReader.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReader.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReader.java Fri Nov 13 23:46:06 2009
@@ -40,23 +40,24 @@
* @throws MetadataReaderException
* @throws RepositoryException
*/
- public byte[] readRawData( ArtifactMetadata bmd, String classifier, String type, boolean exempt )
+ byte[] readRawData( ArtifactMetadata bmd, String classifier, String type, boolean exempt )
throws MetadataReaderException;

- public byte[] readRawData( ArtifactMetadata bmd, String classifier, String type )
+ byte[] readRawData( ArtifactMetadata bmd, String classifier, String type )
throws MetadataReaderException;

/**
- * read metadata for the artifact, pointed by bmd. It will return POM bytes regardless of actual bmd type
+ * read metadata for the artifact, pointed by bmd. It will return POM bytes regardless of actual
+ * bmd type
*
* @param bmd metadata to read
* @param exempt - if this read should be exempt from stream verification, default - false
* @return
* @throws MetadataReaderException
*/
- public byte[] readMetadata( ArtifactMetadata bmd, boolean exempt )
+ byte[] readMetadata( ArtifactMetadata bmd, boolean exempt )
throws MetadataReaderException;

- public byte[] readMetadata( ArtifactMetadata bmd )
+ byte[] readMetadata( ArtifactMetadata bmd )
throws MetadataReaderException;
}

Modified: maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReaderException.java
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReaderException.java?rev=836061&r1=836060&r2=836061&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReaderException.java (original)
+++ maven/mercury/trunk/mercury-core/src/main/java/org/apache/maven/mercury/builder/api/MetadataReaderException.java Fri Nov 13 23:46:06 2009
@@ -32,6 +32,7 @@
*/
public MetadataReaderException()
{
+ // nothing
}

/**

From forum: Maven - Commits

Re: Archive 2.0.11

2009-11-13T15:33:17Z

It has been tagged for several months, I just needed to push it to a vote. After doing the release notes stuff, I was planning to next week, I just got hung up on that.

- Brett

On 14/11/2009, at 9:11 AM, Paul Benedict wrote:

> Since 2.0.11 is totally stagnant, I propose the JIRA version gets
> archived. I don't foresee a release in the future. Does anyone?
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Maven Developers

Commented: (MNG-4443) gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]

2009-11-13T15:24:55Z

[ http://jira.codehaus.org/browse/MNG-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198277#action_198277 ]

Benjamin Bentmann commented on MNG-4443:
----------------------------------------

Could you also attach the debug log of a successful build by Maven 2.x? The missing plugin versions in your build make it otherwise hard to locate actual differences.

From forum: Maven - Issues

Re: RAD 7.5 + m2eclipse + WTP questions...

2009-11-13T15:12:27Z

Doh! I went to the Maven download page before, but apparently didn't think to scroll down far enough to see 3.0-alpha-3. I see it now. :-) Thanks!

On Fri, Nov 13, 2009 at 3:56 PM, Igor Fedorenko <igor@...> wrote:

You can download maven 3.0-alpha-3 from [1]. Building m2e should be as
simple as running "mvn clean install" from org.maven.ide.eclipse.parent
project.

Setting up m2e dev env is explained in [2].

[1] http://maven.apache.org/download.html
[2] https://docs.sonatype.org/display/M2ECLIPSE/Developer+Guide

--
Regards,
Igor

Tim Schwenk wrote:

Yeah, I'm doing some testing with Eclipse 3.5 and JBoss Tools right now. It looks like most of the things that don't work in RAD work just fine with Eclipse + JBT. For some reason, m2eclipse keeps removing my "EAR libraries" classpath container from my web project in RAD, but it leaves it alone in Eclipse. I think this is a major part of my problem, but I have no idea why it's happening.

I've also checked out a copy of the latest m2eclipse source code and I'm digging into the WTP related code to see if I can figure out what exactly is going on. I'm afraid it might take a while for me to even get everything to build because I seem to be missing a Maven 3.0-SNAPSHOT dependency. Also, it looks like I need to have Maven 3.0 to even build the m2eclipse project - is that true? If so, where can I get it?

Thanks for the suggestion of provided rather than optional. What you say makes perfect sense, but I swear I tried doing just that a while back and didn't have any luck. Although, I've learned a lot about the behavior of m2eclipse since then, so maybe I'll get it working this time. I'll go back to RAD this afternoon and see if I can make any headway.

If you could write a tutorial, that would be terrific. If I have any success, I'll try to write something up for RAD users - assuming there actually is anything that needs to be done differently...

-Tim

On Fri, Nov 13, 2009 at 9:38 AM, Fred Bricon <fbricon@... <mailto:fbricon@...>> wrote:

Hi,

Using EARs with m2e/WTP is doable. I don't use RAD but JBoss Tools
instead.
Hint : don't rely on the manifest
- use provided rather than optional dependencies in the webapp
- tell your ear project to deploy dependencies to /lib
- the webapp will compile using the maven library
- at runtime, the webap will find libraries in its ear lib folder

I'll try to write down a tutorial this week-end.

regards,

Fred Bricon

On Fri, Nov 13, 2009 at 2:52 PM, Tim Schwenk <tim.schwenk@...
<mailto:tim.schwenk@...>> wrote:

On Thu, Nov 12, 2009 at 6:08 PM, Murray Waters
<murray.waters@... <mailto:murray.waters@...>> wrote:

I have been through the pain that you have. We use RAD7.5
and WAS 6.1 here too.

I don't think that your problems are generally RAD (in the
RAD extending eclipse sense) but it makes it very difficult
to report bugs doesn't it - you just have no idea if it is
RAD or m2eclipse that is causing you grief. Unfortunately
the developers have publicly said that WTP support will
remain in Alpha for the forseable future. Its the usual
story, if you don't like it then step up and contribute but
like you I have neither the time nor skillset to do so. It
also makes it difficult because ejb isn't supported by
vanilla eclipse so if you want to track down m2eclipse bugs
relating to ejb you have to look at some of the open source
eclipse variants (JBoss tools?) that do so and all of a
sudden you have wasted a week trying to learn Jboss.
Likewise if you want to reliably report bugs in m2eclipse
WTP then you have to make your project tomcat ready or
perhaps JBoss ready instead of Websphere-ready since the
developers are not going to have a copy of RAD. I blame IBM
for only supporting WAS from within RAD and not vanilla
eclipse, it would be so much easier if they did!!!

Well, the fact that WAS is supported only in RAD is probably no
mistake. If I was able to deploy to a WAS test server from
within Eclipse, I would have no reason for using RAD. Although,
now that WAS is free for development use, I suppose there is
some remote hope of eventually getting a WTP connector that
works with Eclipse. There was a semi-functional one for WAS
6.0, but it wasn't nearly as usable as what comes with RAD. I
actually started a project to create a WTP connector for WAS 7.0
(thinking that by the time I have anything remotely usable,
we'll be off of 6.1), but I haven't gotten anywhere with it.

Its a real shame because its in the WTP area that m2eclipse
would really be useful and the problems have been there for
some time. Hopefully as time goes on it gets sorted out and
cleared up.

Personally, my approach to all of this is:
- Dont use EJB. For our old projects that do use EJB and
don't use spring etc, we steer clear of m2eclipse.

Heh. Virtually all of our existing projects use at least some
EJB - whether they need to or not.

- Skip using WTP and use GWT and hosted mode. We were
fortunate in that we decided to make the move from Struts to
GWT for new projects recently, so we no longer have to use
WTP because GWT hosted mode and the gwt-maven plugin does
all of this for us. This leaves us with an m2eclipse
environment with just ears, wars and jars with the war
section not needing to use WTP, and it is quite reliable and
does the job well - this is where m2eclipse really shines.

Oh, that sounds nice, but I'm afraid that GWT is going to be a
non-starter in our organization. There is a lot of resistance
to change.

- When you do see funky things going on and are trying to
track down problems with m2eclipse, pay close attention to
org.eclipse.* files under the .settings folder in your
workspace. Save them and use a diff tool to see what gets
changed at the point where things go wrong. You never know
you might be able to report a bug based on this if you are
lucky.

I've intentionally checked all of those folders into SVN for
exactly this reason. I've been watching them closely, and it
seems that org.eclipse.wst.common.component is the only one that
changes regularly and causes breakage. The rest of them seem
pretty benign. Unfortunately, I don't know whether anything I
find will be sufficient to report a bug.

Murray

On Fri, Nov 13, 2009 at 8:33 AM, Tim Schwenk
<tim.schwenk@... <mailto:tim.schwenk@...>> wrote:

Hi all,

I've been struggling (off and on) for quite some time to
get m2eclipse working properly with the development
stack that we use here at work - which consists of IBM
RAD 7.5 and WAS 6.1/7.0. I've had some minor success,
but there are just a few things that I simply can't seem
to get working, and I'm not sure whether the blame lies
with me, RAD, m2eclipse, or a combination of all three.
In a nutshell, here's what I'm up against...

Since we deploy to WAS, all of our projects are packaged
as EARs. We structure things such that there is a Maven
parent project, an EAR project, a WAR project, and/or an
EJB project as peer directories - i.e. the modules refer
to parents with a relative path of ../parent. In most
cases, I try to create "skinny" WARs - i.e. dependencies
pushed up into the EAR. Of course, there are always a
few deps (like Struts) that need to stay in the WAR, so
the build/packaging gets a little bit tricky, but I've
done it enough now that I pretty much understand the
process. Now, I have no problem checking a project out
of SVN, running a Maven build, and deploying the
resulting EAR to a WAS server - it's when I bring RAD
7.5, WTP, WAS test servers, and m2eclipse into the
picture that things get ugly.

There are large parts of m2eclipse that work perfectly
for me, and I couldn't be happier about that! In
particular, the POM editor, the embedded Maven, the
"Maven Dependencies" classpath container are all
terrific. Here's where the pain begins... If I have,
for example, an EAR project with a WAR module, an EJB
module, and a library JAR module, and the WAR depends on
the JAR and EJB (through workspace resolution), I
absolutely cannot find a way to get the project to
consistently deploy to the WAS test server and setup the
runtime classpath correctly.

Through trial and error, I've learned a few things:

1. Unless I set <bundleFileName> in the maven-ear-plugin
configuration for each of my modules, RAD/WTP/WAS don't
all agree on whether the module name should or shouldn't
have the version number appended. Honestly, at this
point, I can't remember which was the troublemaker, but
setting <bundleFileName> was the solution.

2. If I set <warSourceDirectory> in the maven-war-plugin
to something like ${basedir}/WebContent, strange things
happen. RAD/WTP/m2eclipse seem to think that the
directory should be relative to the project location and
creates a directory under your project named after the
absolute path to your WebContent directory. Also,
m2eclipse or WTP updates the
.settings/org.wst.common.components file with a new
wb-resource containing this full path - and continues to
add a new one every time you do a Maven->Update project
configuration! When I looked, there were about a dozen
of the same entries. The solution to this was to
specify <warSourceDirectory> as just "WebContent".
After that, everyone seems happy.

3. The way that I have been creating skinny WARs was to
set <optional>true</optional> on any WAR dependencies
that I wanted to go in the MANIFEST.MF, but not in
WEB-INF/lib. This works fine when running a Maven
build, but m2eclipse doesn't seem to understand it at
all. I found that using <packagingExcludes> does
however get m2eclipse to update my MANIFEST.MF.
Unfortunately, this is a less than ideal solution
because it's sometimes tricky to come up with a set of
packaging exclusions without repeating things that
you've already declared in the dependencies section, and
any dependencies that are supposed to get packaged in
WEB-INF/lib are not correctly added to the
.settings/org.wst.common.components file, so they aren't
on the runtime classpath when the app is deployed to the
WAS test server.

So, this leads me to the following questions:

1. What is the correct way to configure my dependencies,
the maven-ear-plugin, and the maven-war-plugin in order
to get RAD/WTP/WAS to understand which of my WAR
dependencies should be listed in MANIFEST.MF and
expected in the EAR, and which should be listed in
.settings/org.wst.common.component such that they appear
to be in the WEB-INF/lib of my WAR?

2. Is this something that is even supported by the
current bleeding edge DEV build of m2eclipse 0.9.9?
Will it be supported in 1.0?

3. Can anyone take a guess at whether my problem is
specifically related to RAD, or does it also affect
vanilla Eclipse, or am I just dreaming to think that
this should work in either? (I'm going to try the same
things in Eclipse 3.5 when I get a chance, but I just
haven't gotten around to it yet.)

4. What other information could I provide to help
resolve this problem? I could probably whip up a set of
sample projects, but if nobody else has RAD7.5, I'm not
sure how much that will help.

I'd really like to be able to dig in and help fix this
myself, but I just don't have the free time to do it.
Maybe I'll checkout the source and poke around a little
to see if I can find some obvious bug or gap, but even
that probably won't happen. :-(

Any help is appreciated, and thanks to everyone
contributing to m2ecipse - its getting very close to
making my life much easier. :-)

-Tim

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: Maven Eclipse - User

svn commit: r836054 - /maven/mercury/trunk/pom.xml

2009-11-13T15:08:48Z

Author: olamy
Date: Fri Nov 13 23:08:48 2009
New Revision: 836054

URL: http://svn.apache.org/viewvc?rev=836054&view=rev
Log:
use last maven-parent

Modified:
maven/mercury/trunk/pom.xml

Modified: maven/mercury/trunk/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/pom.xml?rev=836054&r1=836053&r2=836054&view=diff
==============================================================================
--- maven/mercury/trunk/pom.xml (original)
+++ maven/mercury/trunk/pom.xml Fri Nov 13 23:08:48 2009
@@ -23,7 +23,7 @@
<parent>
<groupId>org.apache.maven</groupId>
<artifactId>maven-parent</artifactId>
- <version>11</version>
+ <version>15</version>
</parent>

<groupId>org.apache.maven.mercury</groupId>

From forum: Maven - Commits

svn commit: r836050 - in /maven/mercury/trunk/mercury-maven: mercury-compare-maven-plugin/pom.xml mercury-compare-mdo/pom.xml mercury-compare-mercury/pom.xml

2009-11-13T15:00:31Z

Author: olamy
Date: Fri Nov 13 23:00:31 2009
New Revision: 836050

URL: http://svn.apache.org/viewvc?rev=836050&view=rev
Log:
fix some versions

Modified:
maven/mercury/trunk/mercury-maven/mercury-compare-maven-plugin/pom.xml
maven/mercury/trunk/mercury-maven/mercury-compare-mdo/pom.xml
maven/mercury/trunk/mercury-maven/mercury-compare-mercury/pom.xml

Modified: maven/mercury/trunk/mercury-maven/mercury-compare-maven-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-maven/mercury-compare-maven-plugin/pom.xml?rev=836050&r1=836049&r2=836050&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-maven/mercury-compare-maven-plugin/pom.xml (original)
+++ maven/mercury/trunk/mercury-maven/mercury-compare-maven-plugin/pom.xml Fri Nov 13 23:00:31 2009
@@ -23,7 +23,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0-alpha-5-SNAPSHOT</version>
+ <version>1.0-alpha-8-SNAPSHOT</version>
</parent>

<groupId>org.sonatype.maven.plugins</groupId>
@@ -65,7 +65,7 @@
<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-compare-mdo</artifactId>
- <version>${project.parent.version}</version>
+ <version>${project.version}</version>
</dependency>

<dependency>

Modified: maven/mercury/trunk/mercury-maven/mercury-compare-mdo/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-maven/mercury-compare-mdo/pom.xml?rev=836050&r1=836049&r2=836050&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-maven/mercury-compare-mdo/pom.xml (original)
+++ maven/mercury/trunk/mercury-maven/mercury-compare-mdo/pom.xml Fri Nov 13 23:00:31 2009
@@ -23,7 +23,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0-alpha-5-SNAPSHOT</version>
+ <version>1.0-alpha-8-SNAPSHOT</version>
</parent>

<artifactId>mercury-compare-mdo</artifactId>
@@ -38,12 +38,14 @@
<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-artifact</artifactId>
+ <version>1.0.0-alpha-4</version>
</dependency>


<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-util</artifactId>
+ <version>1.0.0-alpha-4</version>
</dependency>
</dependencies>

Modified: maven/mercury/trunk/mercury-maven/mercury-compare-mercury/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-maven/mercury-compare-mercury/pom.xml?rev=836050&r1=836049&r2=836050&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-maven/mercury-compare-mercury/pom.xml (original)
+++ maven/mercury/trunk/mercury-maven/mercury-compare-mercury/pom.xml Fri Nov 13 23:00:31 2009
@@ -23,7 +23,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0-alpha-5-SNAPSHOT</version>
+ <version>1.0-alpha-8-SNAPSHOT</version>
</parent>

<groupId>org.sonatype.maven.plugins</groupId>
@@ -59,6 +59,7 @@
<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-md-sat</artifactId>
+ <version>1.0.0-alpha-4</version>
</dependency>

<dependency>
@@ -70,6 +71,7 @@
<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-repo-remote-m2</artifactId>
+ <version>1.0.0-alpha-4</version>
</dependency>
</dependencies>

From forum: Maven - Commits

Encrypted Passwords

2009-11-13T14:51:53Z

Howdy,

According to the original feature request for encrypted passwords (http://issues.jfrog.org/jira/browse/RTFACT-1191), the admin user should be able to set the key value:
The basic concept is to allow an admin user the ability (via Web UI) to set a secret key value (javax.crypto.SecretKey) to be used for encrypting users passwords. Once the secret key has been set, the normal user would use the Web UI to input his password and then generate the encrypted (Triple DES?) version of the password. The user would then cut-and-paste the encrypted string into the settings.xml file.
Was this part implemented? If so, how does one go about doing this?

Otherwise, how is the key set and what security controls are around the key?

We are integrating with LDAP, so we just want to be sure our domain credentials are well protected.

Thanks,
Barry

From forum: Artifactory-Users

svn commit: r836042 - /maven/mercury/trunk/mercury-it/pom.xml

2009-11-13T14:46:31Z

Author: olamy
Date: Fri Nov 13 22:46:30 2009
New Revision: 836042

URL: http://svn.apache.org/viewvc?rev=836042&view=rev
Log:
remove dependency declared twice.

Modified:
maven/mercury/trunk/mercury-it/pom.xml

Modified: maven/mercury/trunk/mercury-it/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-it/pom.xml?rev=836042&r1=836041&r2=836042&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-it/pom.xml (original)
+++ maven/mercury/trunk/mercury-it/pom.xml Fri Nov 13 22:46:30 2009
@@ -155,11 +155,6 @@
<version>3.0-20090213.183824-24</version>
</dependency>
-->
- <dependency>
- <groupId>org.mortbay.jetty</groupId>
- <artifactId>jetty-servlet-tester</artifactId>
- </dependency>
-

<dependency>
<groupId>org.sonatype.spice</groupId>

From forum: Maven - Commits

Updated: (ARCHETYPE-220) Unable to access remote catalogs on HTTPS protocol, even with redirection

2009-11-13T14:39:55Z

[ http://jira.codehaus.org/browse/ARCHETYPE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Rigdon updated ARCHETYPE-220:
---------------------------------------

Attachment: https.patch

Why not just allow https as an acceptable url for archetypeCatalog?

> Unable to access remote catalogs on HTTPS protocol, even with redirection
> -------------------------------------------------------------------------
>
> Key: ARCHETYPE-220
> URL: http://jira.codehaus.org/browse/ARCHETYPE-220
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
> Affects Versions: 2.0-alpha-4
> Environment: Any (Windows, Linux)
> Reporter: Josep F. Barranco
> Priority: Minor
> Attachments: https.patch, org.apache.maven.archetype.maven-archetype-ARCHETYPE-220.patch
>
>
> I use that test:
> 1 - Create an "archetype-catalog.xml" and set it on your apache "htdocs" directory
> Executing "mvn archetype:generate -DarchetypeCatalog=http://localhost" works fine.
> 2 - Configure your apache to use certificates and allow SSL (port 443) to access to same archetype catalog file
> Executing "mvn archetype:generate -DarchetypeCatalog=https://localhost" does not work. (it shows default catalog)
> It seems that stating with "https://" does not match with allowed parameter values (local, internal, file:, http:)
> 3 - Anyway, try to redirect your working HTTP access to HTTPS (configure rewrite engine on Apache) as workaround to access you SSL catalog.
> Executing "mvn archetype:generate -DarchetypeCatalog=http://localhost" (same as step 1) IS NOT WORKING!!! (it shows empty catalog)
> There's no way to access an archetype-catalog.xml located on a SSL url ?

From forum: Maven - Issues

Commented: (MNG-4442) Classworlds launcher can't be found on Mac OS X

2009-11-13T14:32:55Z

[ http://jira.codehaus.org/browse/MNG-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198274#action_198274 ]

Tiago Fernandez commented on MNG-4442:
--------------------------------------

Thanks guys for checking this out so quickly!

Matt's tips got the issue fixed for me: "/usr/bin/mvn" was really in the way.
Cheers.

> Classworlds launcher can't be found on Mac OS X
> -----------------------------------------------
>
> Key: MNG-4442
> URL: http://jira.codehaus.org/browse/MNG-4442
> Project: Maven 2
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.0-alpha-3
> Environment: Mac OS X 10.5.8
> Reporter: Tiago Fernandez
> Assignee: Benjamin Bentmann
>
> After installing Maven 3.0-alpha-3 on Windows I can check its version without any problem, but that's not the case for OS X:
> MacBook-Pro:~ tiago$ mvn -v
> Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher
> Renaming ${M2_HOME}/boot/plexus-classworlds-2.2.2.jar to ${M2_HOME}/boot/classworlds-2.2.2.jar fixes the issue, but I am sure this ain't the proper fix.
> Possibly related issue: MNG-2692

From forum: Maven - Issues

Commented: (MNG-4442) Classworlds launcher can't be found on Mac OS X

2009-11-13T14:20:55Z

[ http://jira.codehaus.org/browse/MNG-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198273#action_198273 ]

Matt Raible commented on MNG-4442:
----------------------------------

This worked for me:

sudo rm /usr/bin/mvn
source ~/.bashrc

From forum: Maven - Issues

Updated: (MRESOURCES-104) while filtering resources the token replacement stops at the character @

2009-11-13T14:14:55Z

[ http://jira.codehaus.org/browse/MRESOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll updated MRESOURCES-104:
---------------------------------------

Priority: Major (was: Minor)

agreed

> while filtering resources the token replacement stops at the character @
> -------------------------------------------------------------------------
>
> Key: MRESOURCES-104
> URL: http://jira.codehaus.org/browse/MRESOURCES-104
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Java 1.6.0_16
> Reporter: Thomas Fahrmeyer
> Fix For: 2.5
>
>
> Create a simple file hello.txt under src/main/resources with following content:
> "
> This property ${testProperty} was replaced
> but the one behind a @ will not be processed, as you
> see: ${testProperty}. You shouldn't see a property reference.
> "
> define a build section in your pom.xml like this
> <build>
> <resources>
> <resource>
> <directory>src/main/resources</directory>
> <filtering>true</filtering>
> <includes>
> <include>**/*.txt</include>
> </includes>
> </resource>
> <resource>
> <directory>src/main/resources</directory>
> <filtering>false</filtering>
> <excludes>
> <exclude>**/*.txt</exclude>
> </excludes>
> </resource>
> </resources>
> Run the command:
> mvn process-resources -DtestProperty=IwasReplaced
> this produces the output
> "
> This property IwasReplaced was replaced
> but the one behind a @ will not be processed, as you
> see: ${testProperty}. You shouldn't see a property reference.
> "
> As you see, the second property reference was not resolved. The replacement just stops after the @ character.

From forum: Maven - Issues