date:20091022

[jira] Subscription: Design & Best Practices

2009-10-22 Thread jira

Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist

Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-2584Rebuild on pom change
http://jira.codehaus.org/browse/MNG-2584
MNG-139 server definitions should be reusable - review use of repository IDs
http://jira.codehaus.org/browse/MNG-139
MNG-2125[doc] when and how to define plugins in a pom
http://jira.codehaus.org/browse/MNG-2125
MNG-474 performance improvement for forked lifecycles
http://jira.codehaus.org/browse/MNG-474
MNG-1381best practices: testing strategies
http://jira.codehaus.org/browse/MNG-1381
MNG-1563how to write integration tests
http://jira.codehaus.org/browse/MNG-1563
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.org/browse/MNG-2381
MNG-1950Ability to introduce new lifecycles phases
http://jira.codehaus.org/browse/MNG-1950
MNG-1931add a reportingManagement section
http://jira.codehaus.org/browse/MNG-1931
MNG-1885Uniquely identify modules by module name and version number
http://jira.codehaus.org/browse/MNG-1885
MNG-647 Allow Maven 2 to be monitored using JMX.
http://jira.codehaus.org/browse/MNG-647
MNG-416 best practices:  multiple profile deployments
http://jira.codehaus.org/browse/MNG-416
MNG-367 best practices: multi-user installation
http://jira.codehaus.org/browse/MNG-367
MNG-125 guarded mojo execution
http://jira.codehaus.org/browse/MNG-125
MNG-1569Make build process info read-only to mojos, and provide mechanism 
for explicit out-params for mojos to declare
http://jira.codehaus.org/browse/MNG-1569
MNG-41  best practices: site management
http://jira.codehaus.org/browse/MNG-41
MNG-1441Starting thinking about a proper distributed repository mechanism a 
la CPAN
http://jira.codehaus.org/browse/MNG-1441
MNG-657 possible chicken and egg problem with extensions
http://jira.codehaus.org/browse/MNG-657
MNG-1867deprecate system scope, analyse other use cases
http://jira.codehaus.org/browse/MNG-1867
MNG-868 Use uniform format for  and other tags
http://jira.codehaus.org/browse/MNG-868
MNG-1439Organization Object Model (OOM) 
http://jira.codehaus.org/browse/MNG-1439
MNG-1423best practices: setting up multi-module build
http://jira.codehaus.org/browse/MNG-1423
MNG-1463best practices: plugin inheritance for a multi project build
http://jira.codehaus.org/browse/MNG-1463
MNG-1468best practices: version management in multi project builds
http://jira.codehaus.org/browse/MNG-1468
MNG-1440Developer Object Model (DOM)
http://jira.codehaus.org/browse/MNG-1440
MNG-1425best practices: the location of configuration files vs resources
http://jira.codehaus.org/browse/MNG-1425

You may edit this subscription at:
http://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341&filterId=11471


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

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Brett Porter



On 23/10/2009, at 6:04 AM, Brian Fox wrote:


Just summing up a conversation I had with Jason and Benjamin: After
Benjamin finishes up the current issue MNG-4221
(http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=14719&resolution=-1&sorter/field=issuekey&sorter/order=DESC 
)

then we think it's time to prepare the next Alpha release. This
release won't support reporting plugins and thus sites with reports,
but otherwise it appears to be pretty stable.


Cool, I was about to suggest the same thing again as soon as I get in  
an issue I found yesterday - just needed to check if it was actually a  
POM problem. I'll do that shortly, but I'm fine with or without that  
fix :)


- Brett

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

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Henri Gomez

No problem with both jaxws-maven-plugin 1.10 and the latest one,
jaxws-maven-plugin 1.12.

Sorry for the noise

2009/10/22 Henri Gomez :
> More on this one.
>
> Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with
> the jaxws-maven-plugin 1.11.
> I works with the jaxws-maven-plugin 1.10 :-(
>
> 2009/10/22 Henri Gomez :
>> I just tried a project build with the latest maven 3.0 snapshot
>> (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200))
>>
>> It seems to be a problem with the jaxws-maven-plugin 1.11 :
>>
>> Here is the stack trace :
>>
>> [DEBUG] 
>> /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar
>> [DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar
>> [DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar
>> [DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
>> [DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar
>> [DEBUG] 
>> /Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 7.626s
>> [INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009
>> [INFO] Final Memory: 14M/79M
>> [INFO] 
>> 
>> [ERROR] [0]
>> org.apache.maven.plugin.PluginExecutionException: : : null
>>        at 
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
>>        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:224)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97)
>>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:105)
>>        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:597)
>>        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)
>> Caused by: org.apache.maven.plugin.PluginExecutionException: : null
>>        at 
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
>>        ... 14 more
>> Caused by: java.lang.NullPointerException
>>        at 
>> org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110)
>>        at 
>> org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92)
>>        at 
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
>>        ... 14 more
>> [ERROR]
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [0] 
>> http://cwiki.apa

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Henri Gomez

More on this one.

Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with
the jaxws-maven-plugin 1.11.
I works with the jaxws-maven-plugin 1.10 :-(

2009/10/22 Henri Gomez :
> I just tried a project build with the latest maven 3.0 snapshot
> (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200))
>
> It seems to be a problem with the jaxws-maven-plugin 1.11 :
>
> Here is the stack trace :
>
> [DEBUG] 
> /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
> [DEBUG] 
> /Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar
> [DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar
> [DEBUG] 
> /Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar
> [DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar
> [DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar
> [DEBUG] 
> /Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> [DEBUG] 
> /Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> [DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar
> [DEBUG] 
> /Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar
> [DEBUG] 
> /Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar
> [DEBUG] 
> /Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar
> [DEBUG] 
> /Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 7.626s
> [INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009
> [INFO] Final Memory: 14M/79M
> [INFO] 
> 
> [ERROR] [0]
> org.apache.maven.plugin.PluginExecutionException: : : null
>        at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
>        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:224)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97)
>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:105)
>        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:597)
>        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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: : null
>        at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
>        ... 14 more
> Caused by: java.lang.NullPointerException
>        at 
> org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110)
>        at 
> org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92)
>        at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
>        ... 14 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [0] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>

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

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Henri Gomez

I just tried a project build with the latest maven 3.0 snapshot
(Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200))

It seems to be a problem with the jaxws-maven-plugin 1.11 :

Here is the stack trace :

[DEBUG] 
/Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
[DEBUG] 
/Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar
[DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar
[DEBUG] 
/Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar
[DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar
[DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar
[DEBUG] 
/Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
[DEBUG] 
/Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
[DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar
[DEBUG] 
/Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar
[DEBUG] 
/Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar
[DEBUG] 
/Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar
[DEBUG] 
/Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 7.626s
[INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009
[INFO] Final Memory: 14M/79M
[INFO] 
[ERROR] [0]
org.apache.maven.plugin.PluginExecutionException: : : null
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
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:224)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:105)
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:597)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: : null
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
... 14 more
Caused by: java.lang.NullPointerException
at 
org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110)
at 
org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
... 14 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [0] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

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

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Brian Fox

Yeah I think the site stuff isn't critical for getting feedback on the
core. In fact having it decoupled is bound to save lots of swears
being uttered in many release cycles ;-)

On Thu, Oct 22, 2009 at 3:37 PM, Olivier Lamy  wrote:
> Hi,
> Great.
> Concerning the site plugin this will need a release of some stuff. [1].
> This need some jobs to be really complete (sorry not enough spare atm)
>
> --
> Olivier
> [1] http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
>
> 2009/10/22 Brian Fox :
>> Just summing up a conversation I had with Jason and Benjamin: After
>> Benjamin finishes up the current issue MNG-4221
>> (http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=14719&resolution=-1&sorter/field=issuekey&sorter/order=DESC)
>> then we think it's time to prepare the next Alpha release. This
>> release won't support reporting plugins and thus sites with reports,
>> but otherwise it appears to be pretty stable.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
>
> --
> Olivier
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

Re: preparing for the next 3.x alpha release

2009-10-22 Thread Olivier Lamy

Hi,
Great.
Concerning the site plugin this will need a release of some stuff. [1].
This need some jobs to be really complete (sorry not enough spare atm)

--
Olivier
[1] http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin

2009/10/22 Brian Fox :
> Just summing up a conversation I had with Jason and Benjamin: After
> Benjamin finishes up the current issue MNG-4221
> (http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=14719&resolution=-1&sorter/field=issuekey&sorter/order=DESC)
> then we think it's time to prepare the next Alpha release. This
> release won't support reporting plugins and thus sites with reports,
> but otherwise it appears to be pretty stable.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Olivier

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

preparing for the next 3.x alpha release

2009-10-22 Thread Brian Fox

Just summing up a conversation I had with Jason and Benjamin: After
Benjamin finishes up the current issue MNG-4221
(http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=14719&resolution=-1&sorter/field=issuekey&sorter/order=DESC)
then we think it's time to prepare the next Alpha release. This
release won't support reporting plugins and thus sites with reports,
but otherwise it appears to be pretty stable.

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

Re: Download path for just deployed snapshot

2009-10-22 Thread Brian Fox

The only way to do this reliably would be to go get the metadata from
the repository and use that...it's inside the deploy plugin that this
transformation occurs and it happens based on the metadata that it
just retrieved.

Alternatively you could do this with a repo manager. Nexus provides
rss feeds and it would be trivial to make a plugin to send an email
for new snapshot deployments.

On Thu, Oct 22, 2009 at 11:56 AM, Michal Mally  wrote:
>
> Hello,
>
>  Basically what I need to do is simple mail notification after new snapshot
> is deployed. I plan to attach to deploy phase with plugin that is able to
> send an email and this is no problem. The problem arises when I want to get
> an url for just deployed snapshot to include it in email.
>
>  eg. When artifact com.example.X is deployed to maven repository under
> address http://snapshots.example.com/ I would like to get an url from which
> this atrifact can be downloaded. So something like
> http://snapshots.example.com/com/example/X/1.0-SNAPSHOT/X-1.0--.jar
>
>  I have spent some hours trying to do that - experimenting with Maven API
> with no success yet. As one of my desperate approach I even tried getting
> Metadata for 1.0-SNAPSHOT and then build an URL manually. Unfortunately I
> was never able to resolve it the way the Snapshot.buildNumber and
> Snapshot.timestamp are filled with correct values.
>
>  Could anyone help me with that task. At least which component should be
> used and what is the correct order of execution.
>
>  Thanks in advance.
>
> Best regards,
> Michal Mally
> --
> View this message in context: 
> http://www.nabble.com/Download-path-for-just-deployed-snapshot-tp26012587p26012587.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

Download path for just deployed snapshot

2009-10-22 Thread Michal Mally


Hello,

  Basically what I need to do is simple mail notification after new snapshot
is deployed. I plan to attach to deploy phase with plugin that is able to
send an email and this is no problem. The problem arises when I want to get
an url for just deployed snapshot to include it in email.

  eg. When artifact com.example.X is deployed to maven repository under
address http://snapshots.example.com/ I would like to get an url from which
this atrifact can be downloaded. So something like
http://snapshots.example.com/com/example/X/1.0-SNAPSHOT/X-1.0--.jar

  I have spent some hours trying to do that - experimenting with Maven API
with no success yet. As one of my desperate approach I even tried getting
Metadata for 1.0-SNAPSHOT and then build an URL manually. Unfortunately I
was never able to resolve it the way the Snapshot.buildNumber and
Snapshot.timestamp are filled with correct values.

  Could anyone help me with that task. At least which component should be
used and what is the correct order of execution.  

  Thanks in advance.

Best regards,
Michal Mally
-- 
View this message in context: 
http://www.nabble.com/Download-path-for-just-deployed-snapshot-tp26012587p26012587.html
Sent from the Maven Developers mailing list archive at Nabble.com.


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

Fwd: ASF Board Meeting Summary - October 21, 2009

2009-10-22 Thread Arnaud HERITIER

Congrats Brian,
  It's now official, you are PMC chair.

Cheers,

Arnaud

# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net


-- Forwarded message --
From: Jim Jagielski 
Date: Thu, Oct 22, 2009 at 1:33 AM
Subject: ASF Board Meeting Summary - October 21, 2009
To: committ...@apache.org


The October board meeting took place on the 21th. The following directors
were present:

 Shane Curcuru
 Doug Cutting
 Justin Erenkrantz
 Roy T. Fielding
 Jim Jagielski
 Geir Magnusson, Jr.
 Brian McCallister
 Brett Porter
 Greg Stein

Many guests were present.

The September minutes were approved.

All of the received reports to the board were approved. The following
reports were not received and are expected next month:

 Status report for the Apache Beehive Project
 Status report for the Apache Incubator Project

The following resolutions were passed unaminously:

 A. Update Public Relations Committee Membership (Harvey, VP)
 B. Change of Maven PMC Chair (Brian Fox, VP)
 C. Change the Apache James Project Chair (Norman Maurer, VP)
 D. Change the Apache Xerces Project Chair (Michael Glavassevich, VP)
 E. Change the Public Relations Committee Chair (Shane Curcuru, VP)
 F. Change the Apache Abdera Project Chair (Ant Elder, VP)
 G. Change the Apache Velocity Project Chair (Henning Schmiedehausen, VP)
 H. Establish the Apache PDFBox Project (Andreas Lehmk¸hler, VP)
 I. Update Legal Affairs Committee Membership (Sam Ruby, VP)


The next board meeting will be on the 18th of November.

Re: Build failed in Hudson: m2e-user-issue-votes #257

2009-10-22 Thread Brett Porter


I think this is misconfigured...

- Brett

On 22/10/2009, at 4:00 PM, .COM Hudson wrote:


See 

--
A timer trigger started this job
Building on master
Location 'http://svn.sonatype.org/m2eclipse/trunk/reports' does not  
exist

Updating http://svn.sonatype.org/m2eclipse/trunk/reports
ERROR: Failed to update http://svn.sonatype.org/m2eclipse/trunk/ 
reports

org.tmatesoft.svn.core.SVNException: svn: Target path does not exist
svn: REPORT of '/m2eclipse/!svn/vcc/default': 500 Internal Server  
Error (http://svn.sonatype.org)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error 
(SVNErrorManager.java:64)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error 
(SVNErrorManager.java:51)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport 
(DAVRepository.java:1265)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update 
(DAVRepository.java:820)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.update 
(SVNUpdateClient.java:558)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate 
(SVNUpdateClient.java:401)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate 
(SVNUpdateClient.java:217)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java: 
576)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java: 
543)

at hudson.FilePath.act(FilePath.java:676)
at hudson.FilePath.act(FilePath.java:660)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:536)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:956)
	at hudson.model.AbstractBuild$AbstractRunner.checkout 
(AbstractBuild.java:400)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java: 
349)

at hudson.model.Run.run(Run.java:1117)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java: 
93)

at hudson.model.Executor.run(Executor.java:122)




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

Re: How to retrieve the current maven version from a plugin?

2009-10-22 Thread Mark Hobson

2009/10/22 Brett Porter :
> Well, there's maven-runtime in shared, but that stack dumps on M3 (not sure
> if that's a regression or known incompat.)
>
> Code like this:
>
>  try {
>    System.out.println( runtime.getProject( Mojo.class ).getVersion() );
> } catch ( MavenRuntimeException e ) {
>    throw new MojoExecutionException( e.getMessage(), e );
> }
>
> Error:
>
> [ERROR] : A required class was missing while executing
> test:easy-mojo-plugin:1.0-SNAPSHOT:touch:
> org/apache/maven/project/DuplicateProjectException
>
> I think this is because maven-runtime uses maven-project-2.0.8 as a
> dependency, the exceptions thrown by the project sorter API seem to change
> over time.

Interesting, I haven't tried maven-runtime on M3.  The maven-project
dependency is only required for the MavenRuntime.getProject method
calls, since they return full MavenProject instances.  Try the
MavenRuntime.getProjectProperties methods which return the basic GAV
info instead.

Mark

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

[jira] Subscription: Design & Best Practices

Re: preparing for the next 3.x alpha release

Re: preparing for the next 3.x alpha release

Re: preparing for the next 3.x alpha release

Re: preparing for the next 3.x alpha release

Re: preparing for the next 3.x alpha release

Re: preparing for the next 3.x alpha release

preparing for the next 3.x alpha release

Re: Download path for just deployed snapshot

Download path for just deployed snapshot

Fwd: ASF Board Meeting Summary - October 21, 2009

Re: Build failed in Hudson: m2e-user-issue-votes #257

Re: How to retrieve the current maven version from a plugin?

13 matches

Site Navigation

Mail list logo

Footer information