Nabble - Maven

Re: how to copy jar (also) to target installation dir

2009-11-22T06:21:57Z

It should work with the antrun plugin ( and ant's <copy> task. )

( configure an antrun plugin execution to attach to install phase )

--sony

On Sun, Nov 22, 2009 at 8:43 AM, eyal edri <eyal.edri@...> wrote:

> I want to config the pom project to copy the final jar file to an
> installation dir and bind it to the 'install' phase.
>
> meaning, when i "just" build the project, the jar will be built into the
> default target/project.jar.
>
> but when i "install" it should be also should be copied to
> /usr/local/application/project.jar.
>
> i tried adding "<OutputDirectory> in the 'jar' plugin, but it just changed
> the default target.
>
> --
> Eyal Edri
>

From forum: Maven - Users

Re: how to copy jar (also) to target installation dir

2009-11-22T06:19:36Z

your best bet is to bind an execution of the antrun plugin to the
install phase and use the ant copy task to copy the file for you

Sent from my [rhymes with tryPod] ;-)

On 22 Nov 2009, at 13:43, eyal edri <eyal.edri@...> wrote:

> I want to config the pom project to copy the final jar file to an
> installation dir and bind it to the 'install' phase.
>
> meaning, when i "just" build the project, the jar will be built into
> the
> default target/project.jar.
>
> but when i "install" it should be also should be copied to
> /usr/local/application/project.jar.
>
> i tried adding "<OutputDirectory> in the 'jar' plugin, but it just
> changed
> the default target.
>
> --
> Eyal Edri

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

From forum: Maven - Users

Re: Refactoring question

2009-11-22T06:18:10Z

I find intellij has great refactoring support... and there is now a
free (as in apache licensed) version available

in intellij you just go file | open project, point it at your pom.xml
and it will open your project with everything just configured. then
just drag and drop your java sources into the packages you want
committing as you go and you're done

(netbeans and eclipse have similar support, but in my experience
intellij is best for refactoring)

-Stephen

Sent from my [rhymes with tryPod] ;-)

On 22 Nov 2009, at 13:41, neo anderson <javadeveloper999@...>
wrote:

>
> I use maven 2.0.9, jdk 1.6.0_10 to build my project.
>
> Now I encounter a dilemma. I have source code e.g. example/ioc/
> MyIoc.java,
> example/ioc/tapestry5/MyIocWrapper.java and related Test files. They
> are
> located in different folders at the beginning.
>
> Now I want to reorganize/ refactor the source code. So the structure
> may
> become example/ioc/MyIoc.java, example/ioc/MyIocWrapper.java.
> However, there
> are many classes which has similar situation. That means they may
> just be
> located in different folders.
>
> As I understand, in eclipse a developer can simply right-click and
> choose
> refactoring after modifying the source, then related source code in
> other
> classes would be changed as well. So I would like to know is there any
> chance this can be achieve using maven plugin? Or generally people
> who use
> maven (but don't use eclipse) would recommend the best approach?
>
> I appreciate any suggestion.
>
> Thank you very much.
> --
> View this message in context: http://old.nabble.com/Refactoring-question-tp26464173p26464173.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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

how to copy jar (also) to target installation dir

2009-11-22T05:43:41Z

I want to config the pom project to copy the final jar file to an
installation dir and bind it to the 'install' phase.

meaning, when i "just" build the project, the jar will be built into the
default target/project.jar.

but when i "install" it should be also should be copied to
/usr/local/application/project.jar.

i tried adding "<OutputDirectory> in the 'jar' plugin, but it just changed
the default target.

--
Eyal Edri

From forum: Maven - Users

Refactoring question

2009-11-22T05:41:20Z

I use maven 2.0.9, jdk 1.6.0_10 to build my project.

Now I encounter a dilemma. I have source code e.g. example/ioc/MyIoc.java, example/ioc/tapestry5/MyIocWrapper.java and related Test files. They are located in different folders at the beginning.

Now I want to reorganize/ refactor the source code. So the structure may become example/ioc/MyIoc.java, example/ioc/MyIocWrapper.java. However, there are many classes which has similar situation. That means they may just be located in different folders.

As I understand, in eclipse a developer can simply right-click and choose refactoring after modifying the source, then related source code in other classes would be changed as well. So I would like to know is there any chance this can be achieve using maven plugin? Or generally people who use maven (but don't use eclipse) would recommend the best approach?

I appreciate any suggestion.

Thank you very much.

From forum: Maven - Users

Commented: (MINVOKER-97) Add possibility to inherit settings.xml from calling process

2009-11-22T05:20:55Z

[ http://jira.codehaus.org/browse/MINVOKER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198974#action_198974 ]

Konstantin Titorenko commented on MINVOKER-97:
----------------------------------------------

Don't think that any kind of merge is required, what is needed is ability to use same settings.xml that was used by caller process.
For example, if you run maven if -s key it is not really logical for invoker to ignore that setting.
One possibility would be to add a parameter to run goal of invoker, e.g. inheritSettingsXml=true/false, then in case of true use settings.xml from caller process, current behavior otherwise.

> Add possibility to inherit settings.xml from calling process
> ------------------------------------------------------------
>
> Key: MINVOKER-97
> URL: http://jira.codehaus.org/browse/MINVOKER-97
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Konstantin Titorenko
> Assignee: Olivier Lamy
> Fix For: 1.6
>
>
> Invoker will use default settings xml even if differetn settings xml is specified in calling maven process. It would be very usefull to add posibility to "inherit" settings.xml to invoker:run goal (settingsFile parameter is not enough, since it seems imposible to determine settings file from in calling maven process)

--
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

AW: [VOTE] Release Maven Shade Plugin 1.2.2

2009-11-22T05:09:09Z

+1 nb. works with the 2 projects where I use the shade plugin.

LieGrue,
strub

--- Benjamin Bentmann <benjamin.bentmann@...> schrieb am So, 22.11.2009:

> Von: Benjamin Bentmann <benjamin.bentmann@...>
> Betreff: [VOTE] Release Maven Shade Plugin 1.2.2
> An: "Maven Developers List" <dev@...>
> Datum: Sonntag, 22. November 2009, 13:43
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=15525
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-017/
>
> Staging site (sync pending):
> http://maven.apache.org/plugins/maven-shade-plugin-1.2.2/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com

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

From forum: Maven Developers

[VOTE] Release Maven Shade Plugin 1.2.2

2009-11-22T04:43:48Z

Hi,

We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=15525

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-017/

Staging site (sync pending):
http://maven.apache.org/plugins/maven-shade-plugin-1.2.2/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

+1 from me

Benjamin

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

From forum: Maven Developers

svn commit: r883070 - /maven/plugins/trunk/maven-shade-plugin/pom.xml

2009-11-22T04:33:53Z

Author: bentmann
Date: Sun Nov 22 12:33:52 2009
New Revision: 883070

URL: http://svn.apache.org/viewvc?rev=883070&view=rev
Log:
[maven-release-plugin] prepare for next development iteration

Modified:
maven/plugins/trunk/maven-shade-plugin/pom.xml

Modified: maven/plugins/trunk/maven-shade-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/pom.xml?rev=883070&r1=883069&r2=883070&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-shade-plugin/pom.xml Sun Nov 22 12:33:52 2009
@@ -29,7 +29,7 @@
</parent>

<artifactId>maven-shade-plugin</artifactId>
- <version>1.2.2</version>
+ <version>1.2.3-SNAPSHOT</version>
<packaging>maven-plugin</packaging>

<name>Maven Shade Plugin</name>
@@ -40,9 +40,9 @@
</prerequisites>

<scm>
- <connection>scm:svn:http://svn.apache.org/repos/asf/maven/plugins/tags/maven-shade-plugin-1.2.2</connection>
- <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-shade-plugin-1.2.2</developerConnection>
- <url>http://svn.apache.org/viewvc/maven/plugins/tags/maven-shade-plugin-1.2.2</url>
+ <connection>scm:svn:http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin</connection>
+ <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin</developerConnection>
+ <url>http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin</url>
</scm>
<issueManagement>
<system>jira</system>

From forum: Maven - Commits

svn commit: r883069 - /maven/plugins/tags/maven-shade-plugin-1.2.2/

2009-11-22T04:33:38Z

Author: bentmann
Date: Sun Nov 22 12:33:38 2009
New Revision: 883069

URL: http://svn.apache.org/viewvc?rev=883069&view=rev
Log:
[maven-scm] copy for tag maven-shade-plugin-1.2.2

Added:
maven/plugins/tags/maven-shade-plugin-1.2.2/
- copied from r883068, maven/plugins/trunk/maven-shade-plugin/

From forum: Maven - Commits

svn commit: r883068 - /maven/plugins/trunk/maven-shade-plugin/pom.xml

2009-11-22T04:32:56Z

Author: bentmann
Date: Sun Nov 22 12:32:55 2009
New Revision: 883068

URL: http://svn.apache.org/viewvc?rev=883068&view=rev
Log:
[maven-release-plugin] prepare release maven-shade-plugin-1.2.2

Modified:
maven/plugins/trunk/maven-shade-plugin/pom.xml

Modified: maven/plugins/trunk/maven-shade-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/pom.xml?rev=883068&r1=883067&r2=883068&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-shade-plugin/pom.xml Sun Nov 22 12:32:55 2009
@@ -19,7 +19,7 @@
under the License.
-->

-<project xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd' xmlns='http://maven.apache.org/POM/4.0.0'>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<parent>
@@ -29,7 +29,7 @@
</parent>

<artifactId>maven-shade-plugin</artifactId>
- <version>1.2.2-SNAPSHOT</version>
+ <version>1.2.2</version>
<packaging>maven-plugin</packaging>

<name>Maven Shade Plugin</name>
@@ -40,9 +40,9 @@
</prerequisites>

<scm>
- <connection>scm:svn:http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin</connection>
- <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin</developerConnection>
- <url>http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin</url>
+ <connection>scm:svn:http://svn.apache.org/repos/asf/maven/plugins/tags/maven-shade-plugin-1.2.2</connection>
+ <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-shade-plugin-1.2.2</developerConnection>
+ <url>http://svn.apache.org/viewvc/maven/plugins/tags/maven-shade-plugin-1.2.2</url>
</scm>
<issueManagement>
<system>jira</system>

From forum: Maven - Commits

Re: [VOTE] Release Maven Changes Plugin version 2.2

2009-11-22T03:59:03Z

+1

Vincent

2009/11/20 Dennis Lundberg <dennisl@...>:

> Hi,
>
> We solved 18 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14696
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-012/
>
> Staging site:
> http://maven.apache.org/plugins/maven-changes-plugin-2.2/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> 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: [VOTE] Release Maven JAR Plugin version 2.3

2009-11-22T03:58:37Z

+1

Vincent

2009/11/20 Dennis Lundberg <dennisl@...>:

> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13995
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-013/
>
> Staging site:
> http://maven.apache.org/plugins/maven-jar-plugin-2.3/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
>
> ---------------------------------------------------------------------
> 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: [VOTE] Release Maven Doxia Tools Shared Component version 1.1

2009-11-22T03:58:13Z

+1

Vincent

2009/11/20 Dennis Lundberg <dennisl@...>:

> Hi,
>
> This is the first of a series of releases to get Maven Site Plugin 2.1
> released.
>
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14385
>
> There are no issues left in JIRA!
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-014/
>
> Staging site:
> http://maven.apache.org/shared/maven-doxia-tools-1.1/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
>
> ---------------------------------------------------------------------
> 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

Created: (MAVENUPLOAD-2669) Request to sync "BeanKeeper" repository from sourceforge

2009-11-22T03:18:55Z

Request to sync "BeanKeeper" repository from sourceforge
--------------------------------------------------------

Key: MAVENUPLOAD-2669
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2669
Project: Maven Upload Requests
Issue Type: Wish
Reporter: Robert Brautigam

Hi,

Please sync the m2 repository on sourceforge for project BeanKeeper. I am the admin of this project, proof on sourceforge.

"hu.netmind.beankeeper","mavensync@...:/home/users/d/de/demonsystem/m2","rsync_ssh","Robert Brautigam","demon@...",,

Thanks,
Robert.

--
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

AW: [2.0.11 RC] Please test - RC1

2009-11-22T01:17:55Z

+1 works 4 me

LieGrue,
strub

--- Brett Porter <brett@...> schrieb am Sa, 21.11.2009:

> Von: Brett Porter <brett@...>
> Betreff: [2.0.11 RC] Please test - RC1
> An: "Maven Developers List" <dev@...>
> Datum: Samstag, 21. November 2009, 14:14
> Hi,
>
> I have staged a first release candidate here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
>
> Here are the issues that have been fixed: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118
> in this version.
>
> Please test it out and let us know how it goes -
> particularly if you are currently using 2.0.9 or 2.0.10.
>
> Thanks,
> Brett
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

From forum: Maven Developers

[continuum] BUILD FAILURE: Maven Enforcer - Enforcer Rules - default maven2 buildDefinition

2009-11-22T00:33:24Z

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=249505&projectId=1601

Build statistics:
State: Failed
Previous State: Failed
Started at: Sun 22 Nov 2009 00:33:05 -0800
Finished at: Sun 22 Nov 2009 00:33:11 -0800
Total time: 5s
Build Trigger: Schedule
Build Number: 17
Exit code: 1
Building machine hostname: vmbuild.apache.org
Operating system : Linux(unknown)
Java Home version :
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)

Builder version :
Maven version: 2.0.9
Java version: 1.6.0_06
OS name: "linux" version: "2.6.24-23-server" arch: "i386" Family: "unix"

****************************************************************************
SCM Changes:
****************************************************************************
Changed: stephenc @ Sat 21 Nov 2009 04:40:35 -0800
Comment: [MENFORCER-87] Adding two new parameters to requireNoRepositories which can allow the permission of repositories which are only enabled for snapshots

These two parameters default to false.

In actuality, when true they just ban repositories which are enabled for releases. So you could have a repository which was enabled for nothing, and that would be OK. I see that as being no harm
Files changed:
/maven/enforcer/trunk/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/RequireNoRepositories.java ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/java/org/apache/maven/plugins/enforcer/TestRequireNoRepositories.java ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-plugin-repositories (from /maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/with-plugin-repositories:882884) ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-plugin-repositories/child/pom.xml ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-plugin-repositories/pom.xml ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-repositories (from /maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/with-repositories:882884) ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-repositories/child/pom.xml ( 882889 )
/maven/enforcer/trunk/enforcer-rules/src/test/resources/requireNoRepositories/snapshot-repositories/pom.xml ( 882889 )

****************************************************************************
Dependencies Changes:
****************************************************************************
No dependencies changed

****************************************************************************
Build Definition:
****************************************************************************
POM filename: pom.xml
Goals: clean install
Arguments: --batch-mode --non-recursive
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: DEFAULT_SCHEDULE
Description: default maven2 buildDefinition

****************************************************************************
Test Summary:
****************************************************************************
Tests: 0
Failures: 0
Errors: 0
Total time: 0.0

From forum: Maven - Notifications

Re: [2.0.11 RC] Please test - RC1

2009-11-22T00:32:08Z

Brett Porter schrieb:

> On 22/11/2009, at 2:27 AM, Michael wrote:
>
>> Brett Porter schrieb:
>>> Hi, I have staged a first release candidate here:
>>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
>>> Here are the issues that have been fixed:
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118
>>> in this version. Please test it out and let us know how it goes -
>>> particularly if you are currently using 2.0.9 or 2.0.10.
>> I am currently using 2.0.10 on Win XP SP3 and Ubuntu 8.04 LTS.
>> Running 2.0.11-RC1 only serveral versions of my projects worked as
>> expected!
>
> Thanks for testing it :) Just to clarify - it works as expected on
> all the projects you tried, or it is not working on some projects?
> (I'm a bit confused by "only" here)

Hi Brett,

I am sorry. My fingers were faster than my brain. It was supposed to
mean "on" instead of "only". All projects running with "mvn clean
site-deploy package assembly:assembly" worked fine.

Mike

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

From forum: Maven Developers

Re: MNG-3004/MNG-2802 - Achieving massive parallelity ?

2009-11-21T23:46:03Z

I've looked over the code and thought a bit further about the
constraints involved, and given that:

- Multi module reactor builds are the only interesting targets of
multithreading.
- Reactor builds do not use the "install" output of their upstream
dependencies (I was not aware of that ;)

You do not have to re-order anything at all. An implementation
could just:
A) Immediately fork 1 thread per module for all modules.
B) For the phases compile, install and deploy, a given module can
only proceeed when all its upstream dependencies have completed the same
state
There's still a chance of leaking artifacts to local repository if
upstream deploy fails after install, and the general idea of a
transacted repo would still be nice to stay consistent.

I'm still a bit sure about B) above, it may be a bit limiting in terms
of other usage scenarios. I'm also a bit sure how that'd fit in with all
the other activities in the lifecycle. An alternative would be to
make a declarative-representation of phase-interdependencies that could
express multiple types of concurrency-interdependencies. (But I
consistenly only see one dependency type -
upstreamMustFinishBeforeThisCanStart...?)

Would it float ?

Kristian

lø., 21.11.2009 kl. 11.40 +0000, skrev Stephen Connolly:

> In m3 (which is what we are talking about) AFAIK we can have a
> listener that waits for the end of the start of the deploy phase
> and/or the end of execution.
>
> With a customized install plugin, we could just install to the
> "transaction" repository. The listener can then block until the
> criteria have been met (allowing other modules to progress) That would
> achieve what you're after... namely, produce the artifacts for
> consumption by the other modules before running test and
> integration-test. Once the criteria have been met, we either fail the
> module or we move the artifacts from the "transactional" local repo to
> the real local repo and allow the lifecycle to continue
>
> -Stephen
>
> 2009/11/21 Kristian Rosenvold <kristian.rosenvold@...>:
> > I seem to understand that there's room for several different
> > types of solution here;
> >
> > Starting with the single-machine solution; I now understand that
> > you could start forking downstream builds straight after
> > compile in a reactor build, maybe after install in other cases.
> >
> > In this scenario I think each module is dependant on all upstream
> > modules successfully achieving "install" before proceeding to "deploy".
> > I really think it's important to avoid leaking artifacts that do not
> > have its own (and all upstream) lifecycle requirements fulfilled.
> >
> > When it comes to clustering there may be several approaches:
> > If you decide to publish artifacts through "deploy" to any kind
> > of repo I believe these require to have all lifecycle requirements met,
> > which at my current understanding seems orthogonal to local out-of-order
> > execution.
> >
> > Wouldn't it be feasible to distribute the "local" and perhaps
> > "transacted local" repo inside the cluster using network
> > file sharing ? One would still have to solve serialization issues
> > and using installed artifacts in a reactor build..?
> >
> > The clustering case seems like a much harder task than achieving
> > full local concurrency. I did some fairly extensive measurements
> > with my current build when I set up concurrent spring/junit testing:
> >
> > Missing concurrency in classloading is the most important reason
> > why unit tests run slowly (classloading is strictly a synchronized
> > business until jdk7). By running tests out-order on my local
> > unit test-build I am fairly certain I could reduce run-time
> > for "mvn clean install" to something much closer to "mvn
> > -Dmaven.test.skip=true clean install" (80->25 seconds in my case).
> > This is even before I start parallelizing the individual modules.
> >
> > I must confess that I've yet to see a build that really needs
> > clustering for any other reason than running tests or other individual
> > tasks (javadoc, site etc). I think I'd be inclined to just distributing
> > those specific tasks in a cluster. If you actually had a decent model of
> > inter-lifecycle phase dependencies (requiredForStarting between phases),
> > you could probably achieve good results by keeping lifecycle execution
> > centralized but ditributing plugin execution ?
> >
> > I suppose I may be narrow-minded on this last one...
> >
> > I will be starting to look at the DefaultLifeCycleExecutor with thoughts
> > of out-of-order execution, maybe dabble around a little.
> >
> > Kristian
> >
> > fr., 20.11.2009 kl. 06.29 -0800, skrev Dan Fabulich:
> >> I've been meaning to reply to your earlier emails (it's been a busy week);
> >> to this I'll just say that moving the "test" phase after the "install"
> >> phase is a fascinating idea, which I personally like, but it seems like a
> >> big violation of the contract for the lifecycle, and I suspect it won't be
> >> popular. :-(
> >>
> >> I've long felt that there should be a phase for testing after "install"
> >> for similar reasons. This might be SLIGHTLY more popular since users
> >> would need to explicitly cause their tests to run during this phase.
> >>
> >> What about users doing multi-machine builds? Earlier this week I wrote
> >> that users desiring to do multi-machine parallelism should deploy their
> >> builds to a remote repository shared between the machines. Should their
> >> tests run post-deploy?
> >>
> >> -Dan
> >>
> >>
> >> Kristian Rosenvold wrote:
> >>
> >> > I've been thinking further about parallelity within maven. The proposed
> >> > solution to MNG-3004
> >> > achieves parallelity by analyzing inter-module dependencies and scheduling
> >> > parallel dependencies in parallel.
> >> >
> >> > A simple further evolution of this would be to collect and download all
> >> > external dependencies
> >> > for all modules immediately.
> >> >
> >> > But this idea has been rummaging in my head while jogging for a week or so:
> >> >
> >> > Would it be possible to achieve super-parallelity by describing
> >> > relationships between phases of the build, and even reordering some of the
> >> > phases ? I'll try to explain:
> >> >
> >> > Assume that you can add transactional ACID (or maybe just AID) abilities
> >> > towards the local
> >> > repo for a full build. Simply put: All writes to a local repo is done in a
> >> > per-process-specific instance of the repo, that can be rolled back if the
> >> > build fails (or pushed to the local repo if
> >> > the build is ok)
> >> >
> >> > If you do that you can re-order the life-cycle for most builds to be
> >> > something like this:
> >> >
> >> > validate
> >> > compile
> >> > package
> >> > install
> >> > test
> >> > integration-test
> >> > deploy
> >> >
> >> > Notice that I just moved all the "test" phases after the "install" phase.
> >> > Theoretically you could start any subsequent modules immediately after
> >> > "install" is done. Running of tests is really the big killer in most
> >> > multi-module projects I see.
> >> >
> >> > Since your commit "push" towards the local repo only happens at the very end
> >> > of the build, you
> >> > will not publish artifacts when tests are failing (at leas not project
> >> > output artifacts)
> >> >
> >> > You could actually make this a generic model that describes deifferent kinds
> >> > of
> >> > dependencies between lifecycle phases of different modules. The dependency I
> >> > immediately
> >> > see is "requiredForStarting" - which could be interpreted as meaning that
> >> > any upstream
> >> > dependencies must have reached at least that phase before the phase can be
> >> > started
> >> > for this project. I'm not sure if there's any value in a generic model, but
> >> > my perspective
> >> > may be limited to what I see on a daily basis.
> >> >
> >> > Would this be feasible ?
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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@...
> >
> >
>
> ---------------------------------------------------------------------
> 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: (MGPG-18) NPE in GpgSigner

2009-11-21T17:46:55Z

[ http://jira.codehaus.org/browse/MGPG-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198926#action_198926 ]

Geoffrey Wiseman commented on MGPG-18:
--------------------------------------

Glad it was helpful.

> NPE in GpgSigner
> ----------------
>
> Key: MGPG-18
> URL: http://jira.codehaus.org/browse/MGPG-18
> Project: Maven 2.x GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-4
> Reporter: Geoffrey Wiseman
> Priority: Minor
>
> If I run "mvn package gpg:sign", this works. If I run "mvn gpg:sign", I get the following stack trace:
> {code}
> java.lang.NullPointerException
> at org.apache.maven.plugin.gpg.GpgSigner.generateSignatureForArtifact(GpgSigner.java:119)
> at org.apache.maven.plugin.gpg.GpgSignAttachedMojo.execute(GpgSignAttachedMojo.java:228)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> {code}
> After running this through a debugger, I can see that this is because the 'file' object (project.getArtifact().getFile()) is null, which seems to be the case any time the artifact wasn't generated in this invocation of Maven. At the very least, this should result in a good error message, although it would be nice if "gpg:sign" would work on an artifact that was previously-generated.

From forum: Maven - Issues

Re: [2.0.11 RC] Please test - RC1

2009-11-21T17:04:29Z

On 22/11/2009, at 2:27 AM, Michael wrote:

> Brett Porter schrieb:
>> Hi,
>> I have staged a first release candidate here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
>> Here are the issues that have been fixed: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118 in this version.
>> Please test it out and let us know how it goes - particularly if you are currently using 2.0.9 or 2.0.10.
>
> I am currently using 2.0.10 on Win XP SP3 and Ubuntu 8.04 LTS. Running 2.0.11-RC1 only serveral versions of my projects worked as expected!

Thanks for testing it :) Just to clarify - it works as expected on all the projects you tried, or it is not working on some projects? (I'm a bit confused by "only" here)

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

From forum: Maven Developers

Re: Archetype plugin in m2eclipse 0.9.9.200911171109

2009-11-21T16:58:54Z

When we finish testing this one... we just started, so don't have a good
idea how long it is going to take yet.

--
Regards,
Igor

stug23 wrote:

> Igor,
>
> When will we see another dev seed update of m2e so that I can try out the
> archetypes?
>
>
> Igor Fedorenko-4 wrote:
>> Can you suggest proper plugin version?
>>
>> --
>> Regards,
>> Igor
>>
>> Snjezana Peco wrote:
>>> Hi,
>>>
>>> m2eclipse 0.9.9.200911171109 contains the
>>> org.maven.ide.components.archetype_common plugin 2.0.1.20090526-1230. It
>>> is the old plugin that includes archetype-common 2.0-alpha-2. The
>>> problem is that the plugin version hasn't been changed in
>>> META-INF/MANIFEST.MF.
>>> The correct plugin is placed in
>>> https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/m2eclipse-updatesite/plugins/org.maven.ide.components.archetype_common_2.0.1.20091110-0001.jar
>>> including archetype-common 2.0-alpha-4.
>>> archetype-common 2.0-alpha-4 fixes a lot of issues related to the
>>> archetypes.
>>>
>>> Snjeza
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>

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

http://xircles.codehaus.org/manage_email

From forum: Maven Eclipse - User

svn commit: r883010 - /maven/plugins/branches/maven-site-plugin-3.x/pom.xml

2009-11-21T14:09:30Z

Author: olamy
Date: Sat Nov 21 22:09:29 2009
New Revision: 883010

URL: http://svn.apache.org/viewvc?rev=883010&view=rev
Log:
upgrade parent version

Modified:
maven/plugins/branches/maven-site-plugin-3.x/pom.xml

Modified: maven/plugins/branches/maven-site-plugin-3.x/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/branches/maven-site-plugin-3.x/pom.xml?rev=883010&r1=883009&r2=883010&view=diff
==============================================================================
--- maven/plugins/branches/maven-site-plugin-3.x/pom.xml (original)
+++ maven/plugins/branches/maven-site-plugin-3.x/pom.xml Sat Nov 21 22:09:29 2009
@@ -25,7 +25,7 @@
<parent>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-plugins</artifactId>
- <version>14</version>
+ <version>16</version>
</parent>

<artifactId>maven-site-plugin</artifactId>

From forum: Maven - Commits

svn commit: r883009 - /maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java

2009-11-21T14:04:34Z

Author: bentmann
Date: Sat Nov 21 22:04:33 2009
New Revision: 883009

URL: http://svn.apache.org/viewvc?rev=883009&view=rev
Log:
o Escaped markup

Modified:
maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java

Modified: maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java?rev=883009&r1=883008&r2=883009&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java (original)
+++ maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java Sat Nov 21 22:04:33 2009
@@ -213,8 +213,8 @@
/**
* The name of the shaded artifactId.
*
- * If you like to change the name of the native artifact, you may use the <build><finalName> setting.
- * If this is set to something different than <build><finalName>, no file replacement
+ * If you like to change the name of the native artifact, you may use the <build><finalName> setting.
+ * If this is set to something different than <build><finalName>, no file replacement
* will be performed, even if shadedArtifactAttached is being used.
*
* @parameter expression="${finalName}"

From forum: Maven - Commits

Closed: (MSHADE-53) Shade createDependencyReducedPom ignores artifacts with classifier

2009-11-21T13:52:55Z

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

Benjamin Bentmann closed MSHADE-53.
-----------------------------------

Resolution: Fixed
Fix Version/s: 1.2.2
Assignee: Benjamin Bentmann

Fixed in [r883007|http://svn.apache.org/viewvc?view=revision&revision=883007], SNAPSHOT deployed

> Shade createDependencyReducedPom ignores artifacts with classifier
> ------------------------------------------------------------------
>
> Key: MSHADE-53
> URL: http://jira.codehaus.org/browse/MSHADE-53
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: Maven 2.0.9
> JDK 1.5.0_12
> Reporter: Jonas Vikstrom
> Assignee: Benjamin Bentmann
> Fix For: 1.2.2
>
> Attachments: ShadeMojo.java.patch
>
>
> When adding a jar to be shaded that has a classifier, it is ignored and will still be in the modified pom.
> Example as follows:
> {code:title=pom.xml|borderStyle=solid}
> ...
> <dependencies>
> 
> <dependency>
> <groupId>org.company.foo</groupId>
> <artifactId>my-ejb</artifactId>
> <version>0.0.1</version>
> <classifier>client</classifier>
> </dependency>
> <dependency>
> <groupId>org.company.foo</groupId>
> <artifactId>domain</artifactId>
> <version>0.0.1</version>
> </dependency>
> ....
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-shade-plugin</artifactId>
> <version>1.2.1</version>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>shade</goal>
> </goals>
> <configuration>
> <shadedArtifactAttached>false</shadedArtifactAttached>
> <createDependencyReducedPom>true</createDependencyReducedPom>
> <artifactSet>
> <includes>
> <include>org.company.foo:my-ejb:client</include>
> <include>org.company.foo:domain</include>
> </includes>
> </artifactSet>
> <excludeTransitive>true</excludeTransitive>
> </configuration>
> </execution>
> </executions>
> </plugin>
> ....
> {code}
> It will shade the two jars, but _my-ejb_ *will stil be in the modified pom*
> Since it annoys me I've fixed the issue, you can find it in the attached patch.
> Usecase: You package an ejb and ejb-client with the usual plugin. And since the dependency tree for said client inherents the one for the main jar, it is preferable to wrap it in a separate module, with for instance the domain-module and with its own sets of dependencies.
> /Jonas

From forum: Maven - Issues

svn commit: r883007 - in /maven/plugins/trunk/maven-shade-plugin/src: it/dep-reduced-pom/ it/dep-reduced-pom/repo/ it/dep-reduced-pom/repo/org/ it/dep-reduced-pom/repo/org/apache/ it/dep-reduced-pom/repo/org/apache/maven/ it/dep-reduced-pom/repo/org/ap...

2009-11-21T13:51:46Z

Author: bentmann
Date: Sat Nov 21 21:51:43 2009
New Revision: 883007

URL: http://svn.apache.org/viewvc?rev=883007&view=rev
Log:
[MSHADE-53] Shade createDependencyReducedPom ignores artifacts with classifier

Added:
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.jar (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.pom
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2-client.jar (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2.pom
maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy (with props)
Modified:
maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml?rev=883007&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml Sat Nov 21 21:51:43 2009
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+
+
+<project>
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.apache.maven.its.shade.drp</groupId>
+ <artifactId>test</artifactId>
+ <version>1.0</version>
+ <packaging>jar</packaging>
+
+ <name>MSHADE-53</name>
+ <description>
+ Test that creation of the dependency reduced POM properly handles dependencies with classifiers.
+ </description>
+
+ <repositories>
+ <repository>
+ <id>shade-it</id>
+ <url>file:///${basedir}/repo</url>
+ <releases>
+ <checksumPolicy>ignore</checksumPolicy>
+ </releases>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ </repository>
+ </repositories>
+
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.maven.its.shade.drp</groupId>
+ <artifactId>a</artifactId>
+ <version>0.1</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.maven.its.shade.drp</groupId>
+ <artifactId>b</artifactId>
+ <version>0.2</version>
+ <classifier>client</classifier>
+ </dependency>
+ </dependencies>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-shade-plugin</artifactId>
+ <version>@project.version@</version>
+ <executions>
+ <execution>
+ <id>attach-shade</id>
+ <phase>package</phase>
+ <goals>
+ <goal>shade</goal>
+ </goals>
+ <configuration>
+ <shadedArtifactAttached>false</shadedArtifactAttached>
+ <createDependencyReducedPom>true</createDependencyReducedPom>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+</project>

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/pom.xml
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.jar
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.jar?rev=883007&view=auto
==============================================================================
Binary file - no diff available.

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.pom
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.pom?rev=883007&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.pom (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/a/0.1/a-0.1.pom Sat Nov 21 21:51:43 2009
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+
+
+<project>
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.apache.maven.its.shade.drp</groupId>
+ <artifactId>a</artifactId>
+ <version>0.1</version>
+ <packaging>jar</packaging>
+
+ <distributionManagement>
+ <repository>
+ <id>maven-core-it</id>
+ <url>file:///${basedir}/repo</url>
+ </repository>
+ </distributionManagement>
+</project>

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2-client.jar
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2-client.jar?rev=883007&view=auto
==============================================================================
Binary file - no diff available.

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2-client.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2.pom
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2.pom?rev=883007&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2.pom (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/repo/org/apache/maven/its/shade/drp/b/0.2/b-0.2.pom Sat Nov 21 21:51:43 2009
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+
+
+<project>
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.apache.maven.its.shade.drp</groupId>
+ <artifactId>b</artifactId>
+ <version>0.2</version>
+ <packaging>jar</packaging>
+
+ <distributionManagement>
+ <repository>
+ <id>maven-core-it</id>
+ <url>file:///${basedir}/repo</url>
+ </repository>
+ </distributionManagement>
+</project>

Added: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy?rev=883007&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy Sat Nov 21 21:51:43 2009
@@ -0,0 +1,8 @@
+File pomFile = new File( basedir, "target/dependency-reduced-pom.xml" );
+assert pomFile.isFile()
+
+def ns = new groovy.xml.Namespace("http://maven.apache.org/POM/4.0.0")
+def pom = new XmlParser().parse( pomFile )
+
+assert pom[ns.modelVersion].size() == 1
+assert pom[ns.dependencies][ns.dependency].size() == 0

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/dep-reduced-pom/verify.groovy
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Modified: maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java?rev=883007&r1=883006&r2=883007&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java (original)
+++ maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java Sat Nov 21 21:51:43 2009
@@ -403,7 +403,7 @@
else if ( !renamed )
{
getLog().info( "Replacing original artifact with shaded artifact." );
- File originalArtifact = project.getArtifact().getFile();;
+ File originalArtifact = project.getArtifact().getFile();
replaceFile( originalArtifact, outputJar );

if ( createSourcesJar )
@@ -721,7 +721,7 @@

dependencies.add( d );

- String id = d.getGroupId() + ":" + d.getArtifactId();
+ String id = getId( d );

if ( artifactsToRemove.contains( id ) )
{
@@ -788,17 +788,26 @@

private String getId( Artifact artifact )
{
- if ( artifact.getClassifier() == null || "jar".equals( artifact.getClassifier() ) )
+ return getId( artifact.getGroupId(), artifact.getArtifactId(), artifact.getClassifier() );
+ }
+
+ private String getId( Dependency dependency )
+ {
+ return getId( dependency.getGroupId(), dependency.getArtifactId(), dependency.getClassifier() );
+ }
+
+ private String getId( String groupId, String artifactId, String classifier )
+ {
+ if ( classifier == null || "jar".equals( classifier ) )
{
- return artifact.getGroupId() + ":" + artifact.getArtifactId();
+ return groupId + ":" + artifactId;
}
else
{
- return artifact.getGroupId() + ":" + artifact.getArtifactId() + ":" + artifact.getClassifier();
+ return groupId + ":" + artifactId + ":" + classifier;
}
}

-
public boolean updateExcludesInDeps( MavenProject project,
List dependencies,
List transitiveDeps )

From forum: Maven - Commits

svn commit: r883006 - /maven/plugins/trunk/maven-shade-plugin/pom.xml

2009-11-21T13:49:14Z

Author: bentmann
Date: Sat Nov 21 21:49:13 2009
New Revision: 883006

URL: http://svn.apache.org/viewvc?rev=883006&view=rev
Log:
o Inherited from maven-plugins:16

Modified:
maven/plugins/trunk/maven-shade-plugin/pom.xml

Modified: maven/plugins/trunk/maven-shade-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/pom.xml?rev=883006&r1=883005&r2=883006&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-shade-plugin/pom.xml Sat Nov 21 21:49:13 2009
@@ -25,7 +25,7 @@
<parent>
<artifactId>maven-plugins</artifactId>
<groupId>org.apache.maven.plugins</groupId>
- <version>14</version>
+ <version>16</version>
</parent>

<artifactId>maven-shade-plugin</artifactId>

From forum: Maven - Commits

Newbie: configuring Doxia APT-to-XHTML conversion with nested section blocks?

2009-11-21T13:36:01Z

Hi --

I'm new to Doxia and am trying to write some APT-based documentation
for a new project. I'd like the resulting documentation to be in XHTML
and to use CSS to configure heading numbering in legal outline format
(1. Section, 1.1 First subsection, 1.2 Second subsection, 1.2.1 A
sub-subsection, etc).

CSS2.1 can handle this if the XHTML document structure matches the
outline. That is, subsections are embedded within sections,
sub-subsections within subsections, etc. The XHTML generated by doxia
places these sections adjacent to each other, rather than embedding
them.

Currently, the generated XHTML looks something like this:

<div class="section">
<h1>My heading</h1>
my text
</div>
<div class="section">
<h2>First subsection<h2>
more text
</div>
<div class="section">
<h2>Second subsection<h2>
more text
</div>

What I'd like is for the two subsections above to be enclosed in the
parent section:

<div class="section">
<h1>My heading</h1>
my text
<div class="section">
<h2>First subsection<h2>
more text
</div>
<div class="section">
<h2>Second subsection<h2>
more text
</div>
</div>

Any suggestions?

Ramon

From forum: Doxia - Users

Closed: (MSHADE-64) Relocating does not work, when an annotation references an enum

2009-11-21T12:49:55Z

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

Benjamin Bentmann closed MSHADE-64.
-----------------------------------

Resolution: Fixed
Fix Version/s: 1.2.2
Assignee: Benjamin Bentmann

Fixed in [r882989|http://svn.apache.org/viewvc?view=revision&revision=882989], SNAPSHOT deployed.

> Relocating does not work, when an annotation references an enum
> ---------------------------------------------------------------
>
> Key: MSHADE-64
> URL: http://jira.codehaus.org/browse/MSHADE-64
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Alexander von Zitzewitz
> Assignee: Benjamin Bentmann
> Priority: Critical
> Fix For: 1.2.2
>
> Attachments: pom.xml
>
>
> You could reproduce the problem with the attached pom.
> The enum class javax.xml.bind.annotation.XmlAccessOrder is referenced by the annotation javax.xml.bind.annotation.XmlAccessorType. While the enum itself is moved correctly the reference from annotation to enum is not. This makes the relocation of this package impossible.

From forum: Maven - Issues

svn commit: r882990 - /maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java

2009-11-21T12:49:07Z

Author: bentmann
Date: Sat Nov 21 20:49:06 2009
New Revision: 882990

URL: http://svn.apache.org/viewvc?rev=882990&view=rev
Log:
o Optimized code

Modified:
maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java

Modified: maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java?rev=882990&r1=882989&r2=882990&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java (original)
+++ maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java Sat Nov 21 20:49:06 2009
@@ -303,21 +303,22 @@
{
String name = (String) object;
String value = name;
+
+ String prefix = "";
+ String suffix = "";
+
+ Matcher m = classPattern.matcher( name );
+ if ( m.matches() )
+ {
+ prefix = m.group( 1 ) + "L";
+ suffix = ";";
+ name = m.group( 2 );
+ }
+
for ( Iterator i = relocators.iterator(); i.hasNext(); )
{
Relocator r = (Relocator) i.next();

- String prefix = "";
- String suffix = "";
-
- Matcher m = classPattern.matcher( name );
- if ( m.matches() )
- {
- prefix = m.group( 1 ) + "L";
- suffix = ";";
- name = m.group( 2 );
- }
-
if ( r.canRelocateClass( name ) )
{
value = prefix + r.relocateClass( name ) + suffix;
@@ -329,8 +330,10 @@
break;
}
}
+
return value;
}
+
return super.mapValue( object );
}

From forum: Maven - Commits

svn commit: r882989 - in /maven/plugins/trunk/maven-shade-plugin: ./ src/it/reloc-enum-ref-from-anno/ src/it/reloc-enum-ref-from-anno/src/ src/it/reloc-enum-ref-from-anno/src/main/ src/it/reloc-enum-ref-from-anno/src/main/java/ src/it/reloc-enum-ref-fr...

2009-11-21T12:45:34Z

Author: bentmann
Date: Sat Nov 21 20:45:33 2009
New Revision: 882989

URL: http://svn.apache.org/viewvc?rev=882989&view=rev
Log:
[MSHADE-64] Relocating does not work, when an annotation references an enum

Added:
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java (with props)
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/
maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java (with props)
Modified:
maven/plugins/trunk/maven-shade-plugin/pom.xml
maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java

Modified: maven/plugins/trunk/maven-shade-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/pom.xml?rev=882989&r1=882988&r2=882989&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-shade-plugin/pom.xml Sat Nov 21 20:45:33 2009
@@ -93,12 +93,12 @@
<dependency>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
- <version>3.1</version>
+ <version>3.2</version>
</dependency>
<dependency>
<groupId>asm</groupId>
<artifactId>asm-commons</artifactId>
- <version>3.1</version>
+ <version>3.2</version>
</dependency>
<dependency>
<groupId>jdom</groupId>
@@ -143,7 +143,7 @@
<plugins>
<plugin>
<artifactId>maven-invoker-plugin</artifactId>
- <version>1.4</version>
+ <version>1.5</version>
<configuration>
<debug>true</debug>
<projectsDirectory>src/it</projectsDirectory>

Added: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties?rev=882989&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties Sat Nov 21 20:45:33 2009
@@ -0,0 +1 @@
+invoker.java.version = 1.5+

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/invoker.properties
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Added: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml?rev=882989&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml Sat Nov 21 20:45:33 2009
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+
+
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.apache.maven.its.shade.rerfa</groupId>
+ <artifactId>test</artifactId>
+ <version>1.0</version>
+ <packaging>jar</packaging>
+
+ <name>MSHADE-64</name>
+ <description>
+ Test that enum references in annotations are properly relocated.
+ </description>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <version>2.0.2</version>
+ <configuration>
+ <source>1.5</source>
+ <target>1.5</target>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-jar-plugin</artifactId>
+ <version>2.1</version>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>2.2</version>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-shade-plugin</artifactId>
+ <version>@project.version@</version>
+ <executions>
+ <execution>
+ <id>shade</id>
+ <phase>package</phase>
+ <goals>
+ <goal>shade</goal>
+ </goals>
+ <configuration>
+ <createDependencyReducedPom>false</createDependencyReducedPom>
+ <relocations>
+ <relocation>
+ <pattern>relocated</pattern>
+ <shadedPattern>hidden</shadedPattern>
+ </relocation>
+ </relocations>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>exec-maven-plugin</artifactId>
+ <version>1.1.1</version>
+ <executions>
+ <execution>
+ <id>run</id>
+ <phase>verify</phase>
+ <goals>
+ <goal>exec</goal>
+ </goals>
+ <configuration>
+ <executable>java</executable>
+ <arguments>
+ <argument>-classpath</argument>
+ <argument>${project.build.directory}/test-1.0.jar</argument>
+ <argument>Main</argument>
+ </arguments>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <version>2.3.1</version>
+ </plugin>
+ </plugins>
+ </build>
+</project>

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/pom.xml
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Added: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java?rev=882989&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java Sat Nov 21 20:45:33 2009
@@ -0,0 +1,35 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+@MyAnno( relocated.MyEnum.YES )
+public class Main
+{
+
+ public static void main( String[] args )
+ throws Exception
+ {
+ MyAnno anno = Main.class.getAnnotation( MyAnno.class );
+ System.out.println( "ANNO: " + anno.value() );
+ if ( !relocated.MyEnum.YES.equals( anno.value() ) )
+ {
+ throw new IllegalStateException( "unexpected value: " + anno.value() );
+ }
+ }
+
+}

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/Main.java
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Added: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java?rev=882989&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java Sat Nov 21 20:45:33 2009
@@ -0,0 +1,26 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+@java.lang.annotation.Retention( java.lang.annotation.RetentionPolicy.RUNTIME )
+public @interface MyAnno
+{
+
+ relocated.MyEnum value();
+
+}

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/MyAnno.java
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Added: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java?rev=882989&view=auto
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java (added)
+++ maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java Sat Nov 21 20:45:33 2009
@@ -0,0 +1,27 @@
+package relocated;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+public enum MyEnum
+{
+
+ YES, NO
+
+}

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java
------------------------------------------------------------------------------
svn:eol-style = native

Propchange: maven/plugins/trunk/maven-shade-plugin/src/it/reloc-enum-ref-from-anno/src/main/java/relocated/MyEnum.java
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision

Modified: maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java?rev=882989&r1=882988&r2=882989&view=diff
==============================================================================
--- maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java (original)
+++ maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java Sat Nov 21 20:45:33 2009
@@ -337,17 +337,32 @@
public String map( String name )
{
String value = name;
+
+ String prefix = "";
+ String suffix = "";
+
+ Matcher m = classPattern.matcher( name );
+ if ( m.matches() )
+ {
+ prefix = m.group( 1 ) + "L";
+ suffix = ";";
+ name = m.group( 2 );
+ }
+
for ( Iterator i = relocators.iterator(); i.hasNext(); )
{
Relocator r = (Relocator) i.next();

if ( r.canRelocatePath( name ) )
{
- value = r.relocatePath( name );
+ value = prefix + r.relocatePath( name ) + suffix;
break;
}
}
+
return value;
}
+
}
+
}

From forum: Maven - Commits

Re: [VOTE] Release Maven Changes Plugin version 2.2

2009-11-21T09:42:34Z

+1

Hervé

Le vendredi 20 novembre 2009, Dennis Lundberg a écrit :

> Hi,
>
> We solved 18 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14
> 696
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&st
> atus=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-012/
>
> Staging site:
> http://maven.apache.org/plugins/maven-changes-plugin-2.2/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

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

From forum: Maven Developers

Re: [VOTE] Release Maven JAR Plugin version 2.3

2009-11-21T09:42:01Z

+1

Hervé

Le samedi 21 novembre 2009, Dennis Lundberg a écrit :

> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13
> 995
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&st
> atus=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-013/
>
> Staging site:
> http://maven.apache.org/plugins/maven-jar-plugin-2.3/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

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

From forum: Maven Developers

Re: [VOTE] Release Maven Doxia Tools Shared Component version 1.1

2009-11-21T09:41:29Z

+1

Hervé

Le samedi 21 novembre 2009, Dennis Lundberg a écrit :

> Hi,
>
> This is the first of a series of releases to get Maven Site Plugin 2.1
> released.
>
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14
> 385
>
> There are no issues left in JIRA!
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-014/
>
> Staging site:
> http://maven.apache.org/shared/maven-doxia-tools-1.1/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

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

From forum: Maven Developers

Re: Archetype plugin in m2eclipse 0.9.9.200911171109

2009-11-21T08:45:37Z

Igor,

When will we see another dev seed update of m2e so that I can try out the archetypes?

Igor Fedorenko-4 wrote:

Can you suggest proper plugin version?

--
Regards,
Igor

Snjezana Peco wrote:
> Hi,
>
> m2eclipse 0.9.9.200911171109 contains the
> org.maven.ide.components.archetype_common plugin 2.0.1.20090526-1230. It
> is the old plugin that includes archetype-common 2.0-alpha-2. The
> problem is that the plugin version hasn't been changed in
> META-INF/MANIFEST.MF.
> The correct plugin is placed in
> https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/m2eclipse-updatesite/plugins/org.maven.ide.components.archetype_common_2.0.1.20091110-0001.jar
> including archetype-common 2.0-alpha-4.
> archetype-common 2.0-alpha-4 fixes a lot of issues related to the
> archetypes.
>
> Snjeza
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

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

http://xircles.codehaus.org/manage_email

From forum: Maven Eclipse - User