[jira] [Created] (MNGSITE-303) svn.apache.org extremely slow
Gary S. Weaver created MNGSITE-303: -- Summary: svn.apache.org extremely slow Key: MNGSITE-303 URL: https://issues.apache.org/jira/browse/MNGSITE-303 Project: Maven Project Web Site Issue Type: Bug Reporter: Gary S. Weaver Couldn't find release notes for maven-help-plugin to determine difference between 2.1.1 and 2.2, so tried: svn checkout http://svn.apache.org/repos/asf/maven/plugins/tags/maven-help-plugin-2.2 maven-help-plugin and it's been going for about an hour and still hasn't finished. My download and upload are > 50Mbps and ping is 69ms according to speedtest.net. My ping is a little slow to that server, but not terrible: PING svn.apache.org (209.188.14.144): 56 data bytes 64 bytes from 209.188.14.144: icmp_seq=0 ttl=48 time=131.753 ms 64 bytes from 209.188.14.144: icmp_seq=1 ttl=48 time=131.515 ms 64 bytes from 209.188.14.144: icmp_seq=2 ttl=48 time=157.468 ms 64 bytes from 209.188.14.144: icmp_seq=3 ttl=48 time=133.915 ms 64 bytes from 209.188.14.144: icmp_seq=4 ttl=48 time=131.596 ms is there a mirror I could use instead that might be faster? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] Commented: (MNG-3262) Problem accessing dependency resource via reflection in maven 2 plugin
[
http://jira.codehaus.org/browse/MNG-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216201#action_216201
]
Gary S. Weaver commented on MNG-3262:
-
Benjamin,
I am familiar with writing custom classloaders (although it has been several
years since I last had to), but could you provide an example of a plugin/source
or example that queries the project dependencies and creates a custom
classloader as you are saying?
Especially if you could provide an example that is close to what I'm trying to
do above.
Thanks in advance! I know your time is valuable and you are busy, but I
appreciate any time you can spare,
Gary
> Problem accessing dependency resource via reflection in maven 2 plugin
> --
>
> Key: MNG-3262
> URL: http://jira.codehaus.org/browse/MNG-3262
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.7
>Reporter: Gary S. Weaver
>Assignee: Benjamin Bentmann
> Attachments: trunk-exampleproject.tgz, trunk-i18nsanity-pt.tgz
>
>
> I've written a Maven 2 mojo that is having trouble instantiating (via
> reflection) a properties resource of dependency that is included as a
> "compile"-scope dependency in the project (pom.xml) that is utilizing my
> plugin.
> (Even though I need the plugin to access a dependency that is in "provided"
> scope, for now I'm using compile scope since the maven documentation states
> that @requiresDependencyResolution doesn't support provided scope.)
> Here are the details:
> 1) I have the following dependency:
> ---start---
>
>
> com.atlassian.confluence
> confluence
> 2.6.0
> compile
>
>
> ---end---
> 2) In the pom.xml of the project that utilizes my plugin, the mojo of the
> plugin I wrote is configured with the execution:
> ---start---
>
> get_ConfluenceActionSupport.properties
> compile
>
> extractProperties
>
>
>
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
>
>
> ---end---
> 3) In the Maven 2 mojo it calls the following code (just copied/pasted the
> relevant portion):
> ---start---
> // load properties with reflection and save to file
> InputStream in = null;
> OutputStream out = null;
> boolean foundFile = false;
> try {
> String resource = cleanResourceName(fullyQualifiedProperties);
> System.out.println("Getting " + resource);
> in = getClass().getResourceAsStream (resource);
> if (in != null)
> {
> Properties result = new Properties();
> result.load (in); // Can throw IOException
> out = new BufferedOutputStream(new
> FileOutputStream(outputPathname));
> result.store(out, "");
> foundFile = true;
> }
> }
> ---end---
> When executed, it can't find the properties file in the classloader. As you
> can see from the following output, I'm putting the resource string together
> correctly as
> "/com/atlassian/confluence/core/ConfluenceActionSupport.properties" which if
> you interrogate the above confluence dependency, you should be able to find.
> ---start---
> [INFO] [i18nsanity-pt:extractProperties {execution:
> get_ConfluenceActionSupport.properties}]
> [INFO] Extracting properties file from classpath...
> fullyQualifiedProperties=com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> outputFile=/usr/svn/community/confluence/plugins/americanenglishlanguagepack/trunk/target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
> Getting /com/atlassian/confluence/core/ConfluenceActionSupport.properties
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed properties extraction!
> Embedded error: Could not find properties file on classpath:
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
> ---end---
> Thanks!
--
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
[jira] Created: (MNG-3262) Problem accessing dependency resource via reflection in maven 2 plugin
Problem accessing dependency resource via reflection in maven 2 plugin
--
Key: MNG-3262
URL: http://jira.codehaus.org/browse/MNG-3262
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.7
Reporter: Gary S. Weaver
I've written a Maven 2 mojo that is having trouble instantiating (via
reflection) a properties resource of dependency that is included as a
"compile"-scope dependency in the project (pom.xml) that is utilizing my plugin.
(Even though I need the plugin to access a dependency that is in "provided"
scope, for now I'm using compile scope since the maven documentation states
that @requiresDependencyResolution doesn't support provided scope.)
Here are the details:
1) I have the following dependency:
---start---
com.atlassian.confluence
confluence
2.6.0
compile
---end---
2) In the pom.xml of the project that utilizes my plugin, the mojo of the
plugin I wrote is configured with the execution:
---start---
get_ConfluenceActionSupport.properties
compile
extractProperties
com.atlassian.confluence.core.ConfluenceActionSupport.properties
target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
---end---
3) In the Maven 2 mojo it calls the following code (just copied/pasted the
relevant portion):
---start---
// load properties with reflection and save to file
InputStream in = null;
OutputStream out = null;
boolean foundFile = false;
try {
String resource = cleanResourceName(fullyQualifiedProperties);
System.out.println("Getting " + resource);
in = getClass().getResourceAsStream (resource);
if (in != null)
{
Properties result = new Properties();
result.load (in); // Can throw IOException
out = new BufferedOutputStream(new
FileOutputStream(outputPathname));
result.store(out, "");
foundFile = true;
}
}
---end---
When executed, it can't find the properties file in the classloader. As you can
see from the following output, I'm putting the resource string together
correctly as
"/com/atlassian/confluence/core/ConfluenceActionSupport.properties" which if
you interrogate the above confluence dependency, you should be able to find.
---start---
[INFO] [i18nsanity-pt:extractProperties {execution:
get_ConfluenceActionSupport.properties}]
[INFO] Extracting properties file from classpath...
fullyQualifiedProperties=com.atlassian.confluence.core.ConfluenceActionSupport.properties
outputFile=/usr/svn/community/confluence/plugins/americanenglishlanguagepack/trunk/target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
Getting /com/atlassian/confluence/core/ConfluenceActionSupport.properties
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed properties extraction!
Embedded error: Could not find properties file on classpath:
com.atlassian.confluence.core.ConfluenceActionSupport.properties
---end---
Thanks!
--
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
[jira] Updated: (MNG-3262) Problem accessing dependency resource via reflection in maven 2 plugin
[
http://jira.codehaus.org/browse/MNG-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary S. Weaver updated MNG-3262:
Attachment: trunk-exampleproject.tgz
trunk-i18nsanity-pt.tgz
Attached two maven2 projects and source:
* trunk-i18nsanity-pt.tgz - the plugin project
(net.sf.i18nsanity.pt.maven.plugin.PropertiesExtractorMojo is the plugin mojo
in question having this trouble)
* trunk-exampleproject.tgz - the project using the plugin that exhibits the
issue
Thanks for any help you can provide in figuring this out.
> Problem accessing dependency resource via reflection in maven 2 plugin
> --
>
> Key: MNG-3262
> URL: http://jira.codehaus.org/browse/MNG-3262
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.7
>Reporter: Gary S. Weaver
> Attachments: trunk-exampleproject.tgz, trunk-i18nsanity-pt.tgz
>
>
> I've written a Maven 2 mojo that is having trouble instantiating (via
> reflection) a properties resource of dependency that is included as a
> "compile"-scope dependency in the project (pom.xml) that is utilizing my
> plugin.
> (Even though I need the plugin to access a dependency that is in "provided"
> scope, for now I'm using compile scope since the maven documentation states
> that @requiresDependencyResolution doesn't support provided scope.)
> Here are the details:
> 1) I have the following dependency:
> ---start---
>
>
> com.atlassian.confluence
> confluence
> 2.6.0
> compile
>
>
> ---end---
> 2) In the pom.xml of the project that utilizes my plugin, the mojo of the
> plugin I wrote is configured with the execution:
> ---start---
>
> get_ConfluenceActionSupport.properties
> compile
>
> extractProperties
>
>
>
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
>
>
> ---end---
> 3) In the Maven 2 mojo it calls the following code (just copied/pasted the
> relevant portion):
> ---start---
> // load properties with reflection and save to file
> InputStream in = null;
> OutputStream out = null;
> boolean foundFile = false;
> try {
> String resource = cleanResourceName(fullyQualifiedProperties);
> System.out.println("Getting " + resource);
> in = getClass().getResourceAsStream (resource);
> if (in != null)
> {
> Properties result = new Properties();
> result.load (in); // Can throw IOException
> out = new BufferedOutputStream(new
> FileOutputStream(outputPathname));
> result.store(out, "");
> foundFile = true;
> }
> }
> ---end---
> When executed, it can't find the properties file in the classloader. As you
> can see from the following output, I'm putting the resource string together
> correctly as
> "/com/atlassian/confluence/core/ConfluenceActionSupport.properties" which if
> you interrogate the above confluence dependency, you should be able to find.
> ---start---
> [INFO] [i18nsanity-pt:extractProperties {execution:
> get_ConfluenceActionSupport.properties}]
> [INFO] Extracting properties file from classpath...
> fullyQualifiedProperties=com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> outputFile=/usr/svn/community/confluence/plugins/americanenglishlanguagepack/trunk/target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
> Getting /com/atlassian/confluence/core/ConfluenceActionSupport.properties
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed properties extraction!
> Embedded error: Could not find properties file on classpath:
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
> ---end---
> Thanks!
--
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
[jira] Commented: (MNG-3262) Problem accessing dependency resource via reflection in maven 2 plugin
[
http://jira.codehaus.org/browse/MNG-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112832
]
Gary S. Weaver commented on MNG-3262:
-
Just curious... wouldn't everyone think that you could load properties from one
of the "provided" scoped dependencies within a maven 2 plugin, or am I smoking
crack?
> Problem accessing dependency resource via reflection in maven 2 plugin
> --
>
> Key: MNG-3262
> URL: http://jira.codehaus.org/browse/MNG-3262
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.7
>Reporter: Gary S. Weaver
> Fix For: 2.0.x
>
> Attachments: trunk-exampleproject.tgz, trunk-i18nsanity-pt.tgz
>
>
> I've written a Maven 2 mojo that is having trouble instantiating (via
> reflection) a properties resource of dependency that is included as a
> "compile"-scope dependency in the project (pom.xml) that is utilizing my
> plugin.
> (Even though I need the plugin to access a dependency that is in "provided"
> scope, for now I'm using compile scope since the maven documentation states
> that @requiresDependencyResolution doesn't support provided scope.)
> Here are the details:
> 1) I have the following dependency:
> ---start---
>
>
> com.atlassian.confluence
> confluence
> 2.6.0
> compile
>
>
> ---end---
> 2) In the pom.xml of the project that utilizes my plugin, the mojo of the
> plugin I wrote is configured with the execution:
> ---start---
>
> get_ConfluenceActionSupport.properties
> compile
>
> extractProperties
>
>
>
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
>
>
> ---end---
> 3) In the Maven 2 mojo it calls the following code (just copied/pasted the
> relevant portion):
> ---start---
> // load properties with reflection and save to file
> InputStream in = null;
> OutputStream out = null;
> boolean foundFile = false;
> try {
> String resource = cleanResourceName(fullyQualifiedProperties);
> System.out.println("Getting " + resource);
> in = getClass().getResourceAsStream (resource);
> if (in != null)
> {
> Properties result = new Properties();
> result.load (in); // Can throw IOException
> out = new BufferedOutputStream(new
> FileOutputStream(outputPathname));
> result.store(out, "");
> foundFile = true;
> }
> }
> ---end---
> When executed, it can't find the properties file in the classloader. As you
> can see from the following output, I'm putting the resource string together
> correctly as
> "/com/atlassian/confluence/core/ConfluenceActionSupport.properties" which if
> you interrogate the above confluence dependency, you should be able to find.
> ---start---
> [INFO] [i18nsanity-pt:extractProperties {execution:
> get_ConfluenceActionSupport.properties}]
> [INFO] Extracting properties file from classpath...
> fullyQualifiedProperties=com.atlassian.confluence.core.ConfluenceActionSupport.properties
>
> outputFile=/usr/svn/community/confluence/plugins/americanenglishlanguagepack/trunk/target/classes/com/atlassian/confluence/core/ConfluenceActionSupport.properties
> Getting /com/atlassian/confluence/core/ConfluenceActionSupport.properties
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed properties extraction!
> Embedded error: Could not find properties file on classpath:
> com.atlassian.confluence.core.ConfluenceActionSupport.properties
> ---end---
> Thanks!
--
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
[jira] Updated: (MNG-2784) Multiple executions of the same plugin at the same life cycle phase in a multi-module profile mixed up
[ http://jira.codehaus.org/browse/MNG-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver updated MNG-2784: Attachment: MNG-2784-issue-with-maven-2.0.9.tar.gz Attaching a project that gives example of mix of different and same plugin with different execution ids in same phase not being executed in order that they appear in pom.xml (and it isn't in reverse order either). Could this issue please be re-opened or explanation given for whether this will be fixed? The other bug referenced was supposedly fixed in 2.0.7, but I am seeing this behavior in 2.0.9. Thanks in advance for your help! > Multiple executions of the same plugin at the same life cycle phase in a > multi-module profile mixed up > -- > > Key: MNG-2784 > URL: http://jira.codehaus.org/browse/MNG-2784 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build, Plugins and Lifecycle, Profiles, > Reactor and workspace >Affects Versions: 2.0.4, 2.0.5 >Reporter: Maik Ebert >Assignee: Jason van Zyl >Priority: Critical > Fix For: 2.0.7 > > Attachments: MNG-2784-issue-with-maven-2.0.9.tar.gz, MNG-2784.patch > > > I use the latest Maven 2.0.5 build found at > http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ > I have multiple executions of the same plugin at the same life cycle phase in > a multi-module parent POM. There was a bug regarding the order of this > executions. This was fixed at 2.0.5. > Now I needed to extract these plugin executions to a profile in this parent > POM. Now the executions are not ordered correctly anymore :-( > Before (works fine): > parent\pom.xml <= multiple executions of the same plugin at the same life > cycle phase in the default build element > parent \child1\pom.xml > parent \child2\pom.xml > Calling mvn install in parent works fine. > After (fails): > parent\pom.xml <= multiple executions of the same plugin at the same life > cycle phase in the build element of a profile > parent \child1\pom.xml > parent \child2\pom.xml > Calling mvn install in parent mixed up the execution order in the childs. -- 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
[jira] Created: (MNG-3719) Need to have a way to either define plugin execution dependencies on other plugin executions having executed first (at least within same lifecycle phase)
Need to have a way to either define plugin execution dependencies on other
plugin executions having executed first (at least within same lifecycle phase)
-
Key: MNG-3719
URL: http://jira.codehaus.org/browse/MNG-3719
Project: Maven 2
Issue Type: Bug
Components: POM
Affects Versions: 2.0.9
Environment: Maven 2.0.9, java version "1.5.0_13" Java(TM) 2 Runtime
Environment, Standard Edition (build 1.5.0_13-b05-241) Java HotSpot(TM) Client
VM (build 1.5.0_13-120, mixed mode, sharing), OS X 10.4
Reporter: Gary S. Weaver
Priority: Critical
Attachments: plugin-execution-order-cant-be-defined-maven-2.0.9.tar.gz
I extend my sincere apologies if there is a much easier way of doing this, but
so far I haven't found any.
There should be some way to ensure order of plugin executions through
dependencies on other executions. See attached project for example, or see
below for the applicable example in a pom.xml. When plugins are defined in
pom.xml in the following manner to ensure correct execution order, they are not
executed sequentially and there is no way to indicate dependencies, as would be
expected (note- I'm not expecting that it interpret the "step 1...", ..., "step
5..." IDs, I'm only suggesting that either the plugins be executed in order
that they are found in the XML (most intuitive) or that there be some concept
of priority/ordinal added, or even perhaps (this would be most "ant-like") that
plugin executions (and maybe even plugin goal executions) be allowed to define
prequisite execution IDs to be run (even if they are IDs not defined in the
pom, but maybe a parent pom, even though I don't need that right now).
I know that this could be problematic if a plugin execution from one lifecycle
phase depends on another from another lifecycle phase (and you could get into
circular references that way that would have to be recognized during pom
validation after loading/merging pom.xmls). However, not being able to at the
very least define order of execution of different (or the same) plugin
executions as noted below and in attached project makes it difficult to chain
plugin executions that depend on each other, thereby reducing the practicality
of the pom.xml and Maven 2.
For example, these plugin executions cannot be ordered properly in Maven 2.0.9,
since there appears to be no way to indicate dependencies of one execution on
another:
{code}
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
org.apache.maven.plugins
maven-antrun-plugin
step 1 - backup-original-web.xml-from-src
generate-resources
run
org.codehaus.mojo
jspc-maven-plugin
step 2 - jspc
generate-resources
compile
org.apache.pluto
pluto-taglib
1.1.3
jar
javax.portlet
portlet-api
1.0
jar
javax.servlet
jstl
1.1.2
jar
taglibs
standard
1.1.2
jar
org.apache.maven.plugins
maven-antrun-plugin
step 3 - copy-jspc-web.xml-atop-web.xml-in-src
generate-resources
run
[jira] Commented: (MNG-2784) Multiple executions of the same plugin at the same life cycle phase in a multi-module profile mixed up
[
http://jira.codehaus.org/browse/MNG-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145198#action_145198
]
Gary S. Weaver commented on MNG-2784:
-
Nevermind attachment MNG-2784-issue-with-maven-2.0.9.tar.gz and my comment - I
created another bug: MNG-3719 ("Need to have a way to either define plugin
execution dependencies on other plugin executions having executed first (at
least within same lifecycle phase")
> Multiple executions of the same plugin at the same life cycle phase in a
> multi-module profile mixed up
> --
>
> Key: MNG-2784
> URL: http://jira.codehaus.org/browse/MNG-2784
> Project: Maven 2
> Issue Type: Bug
> Components: Bootstrap & Build, Plugins and Lifecycle, Profiles,
> Reactor and workspace
>Affects Versions: 2.0.4, 2.0.5
>Reporter: Maik Ebert
>Assignee: Jason van Zyl
>Priority: Critical
> Fix For: 2.0.7
>
> Attachments: MNG-2784-issue-with-maven-2.0.9.tar.gz, MNG-2784.patch
>
>
> I use the latest Maven 2.0.5 build found at
> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/
> I have multiple executions of the same plugin at the same life cycle phase in
> a multi-module parent POM. There was a bug regarding the order of this
> executions. This was fixed at 2.0.5.
> Now I needed to extract these plugin executions to a profile in this parent
> POM. Now the executions are not ordered correctly anymore :-(
> Before (works fine):
> parent\pom.xml <= multiple executions of the same plugin at the same life
> cycle phase in the default build element
> parent \child1\pom.xml
> parent \child2\pom.xml
> Calling mvn install in parent works fine.
> After (fails):
> parent\pom.xml <= multiple executions of the same plugin at the same life
> cycle phase in the build element of a profile
> parent \child1\pom.xml
> parent \child2\pom.xml
> Calling mvn install in parent mixed up the execution order in the childs.
--
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
[jira] Commented: (MNG-3719) Need to have a way to either define plugin execution dependencies on other plugin executions having executed first (at least within same lifecycle phase)
[
http://jira.codehaus.org/browse/MNG-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145199#action_145199
]
Gary S. Weaver commented on MNG-3719:
-
Note: the fact that that associated project's pom.xml and plugin executions
above are tied to the same lifecycle and yet do not execute in order seems to
be a bug with Maven 2, since it states on the lifecycle page in the
documentation
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
that:
"Note: As of Maven 2.0.5, multiple goals bound to a phase are executed in the
same order as they are declared in the POM."
However, it appears that is not working in Maven 2.0.9, because if it were,
then the above pom would execute in order as intended.
I think though that having executions be allowed to specify dependencies on
other executions is probably the better way to do it, wouldn't it be?
> Need to have a way to either define plugin execution dependencies on other
> plugin executions having executed first (at least within same lifecycle phase)
> -
>
> Key: MNG-3719
> URL: http://jira.codehaus.org/browse/MNG-3719
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.9
> Environment: Maven 2.0.9, java version "1.5.0_13" Java(TM) 2 Runtime
> Environment, Standard Edition (build 1.5.0_13-b05-241) Java HotSpot(TM)
> Client VM (build 1.5.0_13-120, mixed mode, sharing), OS X 10.4
>Reporter: Gary S. Weaver
>Priority: Critical
> Attachments: plugin-execution-order-cant-be-defined-maven-2.0.9.tar.gz
>
>
> I extend my sincere apologies if there is a much easier way of doing this,
> but so far I haven't found any.
> There should be some way to ensure order of plugin executions through
> dependencies on other executions. See attached project for example, or see
> below for the applicable example in a pom.xml. When plugins are defined in
> pom.xml in the following manner to ensure correct execution order, they are
> not executed sequentially and there is no way to indicate dependencies, as
> would be expected (note- I'm not expecting that it interpret the "step 1...",
> ..., "step 5..." IDs, I'm only suggesting that either the plugins be executed
> in order that they are found in the XML (most intuitive) or that there be
> some concept of priority/ordinal added, or even perhaps (this would be most
> "ant-like") that plugin executions (and maybe even plugin goal executions) be
> allowed to define prequisite execution IDs to be run (even if they are IDs
> not defined in the pom, but maybe a parent pom, even though I don't need that
> right now).
> I know that this could be problematic if a plugin execution from one
> lifecycle phase depends on another from another lifecycle phase (and you
> could get into circular references that way that would have to be recognized
> during pom validation after loading/merging pom.xmls). However, not being
> able to at the very least define order of execution of different (or the
> same) plugin executions as noted below and in attached project makes it
> difficult to chain plugin executions that depend on each other, thereby
> reducing the practicality of the pom.xml and Maven 2.
> For example, these plugin executions cannot be ordered properly in Maven
> 2.0.9, since there appears to be no way to indicate dependencies of one
> execution on another:
> {code}
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> step 1 - backup-original-web.xml-from-src
> generate-resources
>
> run
>
>
>
>
>
> file="${pom.basedir}/src/main/webapp/WEB-INF/web.xml"
> todir="${pom.basedir}/target/tmpwebxml/"/>
>
>
>
>
>
>
>
> org.codehaus.mojo
> jspc-maven-plugin
>
>
> step 2 - jspc
> generate-resources
>
> compile
>
>
[jira] Created: (MAVENUPLOAD-2197) Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number)
Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number) -- Key: MAVENUPLOAD-2197 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2197 Project: Maven Upload Requests Issue Type: Wish Reporter: Gary S. Weaver Attachments: rupy-0.2.4.jar Rupy ( http://code.google.com/p/rupy/ ) is self described as: "Weighing less than 50KB, rupy is probably the smallest Java NIO application server in the world. Rupy is inherently non-blocking asynchronous, which makes it the ideal candidate for high concurrency real-time applications pushing dynamic data. Tested with acme, rupy performs on average ~1500 requests per second. To put that figure in perspective; acme doesn't use keep-alive, so that means 1500 unique TCP connections serving dynamic content per second! Thanks to NIO and an event queue to avoid selector trashing, this figure degrades gracefully under high concurrency. " Rupy is also mentioned here (where I found reference to it): http://java-source.net/open-source/web-servers I think it would make a good addition to the central Maven 2 repository, and I'd consider using it in a project I'm developing. I also mentioned it on the maven users mailing list. I renamed http.jar in the bundle to rupy-0.2.4.jar to meet convention. It appears to be a final release, even though is versioned as v0.2.4. I will attempt to contact the developer to inform him of this. -- 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
[jira] Commented: (MAVENUPLOAD-2197) Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146856#action_146856 ] Gary S. Weaver commented on MAVENUPLOAD-2197: - Rats. I didn't actually create a bundle. Ignore that Bundle URL. I'll create a bundle and attach it shortly. > Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite > version number) > -- > > Key: MAVENUPLOAD-2197 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2197 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: rupy-0.2.4.jar > > > Rupy ( http://code.google.com/p/rupy/ ) is self described as: "Weighing less > than 50KB, rupy is probably the smallest Java NIO application server in the > world. Rupy is inherently non-blocking asynchronous, which makes it the ideal > candidate for high concurrency real-time applications pushing dynamic data. > Tested with acme, rupy performs on average ~1500 requests per second. To put > that figure in perspective; acme doesn't use keep-alive, so that means 1500 > unique TCP connections serving dynamic content per second! Thanks to NIO and > an event queue to avoid selector trashing, this figure degrades gracefully > under high concurrency. " > Rupy is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I renamed http.jar in the bundle to rupy-0.2.4.jar to meet convention. It > appears to be a final release, even though is versioned as v0.2.4. > I will attempt to contact the developer to inform him of this. -- 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
[jira] Updated: (MAVENUPLOAD-2197) Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver updated MAVENUPLOAD-2197: Attachment: rupy-0.2.4-bundle.jar Ok, here is the real bundle that I just created (attached as rupy-0.2.4-bundle.jar). > Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite > version number) > -- > > Key: MAVENUPLOAD-2197 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2197 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: rupy-0.2.4-bundle.jar, rupy-0.2.4.jar > > > Rupy ( http://code.google.com/p/rupy/ ) is self described as: "Weighing less > than 50KB, rupy is probably the smallest Java NIO application server in the > world. Rupy is inherently non-blocking asynchronous, which makes it the ideal > candidate for high concurrency real-time applications pushing dynamic data. > Tested with acme, rupy performs on average ~1500 requests per second. To put > that figure in perspective; acme doesn't use keep-alive, so that means 1500 > unique TCP connections serving dynamic content per second! Thanks to NIO and > an event queue to avoid selector trashing, this figure degrades gracefully > under high concurrency. " > Rupy is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I renamed http.jar in the bundle to rupy-0.2.4.jar to meet convention. It > appears to be a final release, even though is versioned as v0.2.4. > I will attempt to contact the developer to inform him of this. -- 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
[jira] Commented: (MREPOSITORY-11) Javadoc not included in the bundle
[ http://jira.codehaus.org/browse/MREPOSITORY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146864#action_146864 ] Gary S. Weaver commented on MREPOSITORY-11: --- It looks like the fix version is earlier than 2.1. It appears it is working in 2.0.9. > Javadoc not included in the bundle > -- > > Key: MREPOSITORY-11 > URL: http://jira.codehaus.org/browse/MREPOSITORY-11 > Project: Maven 2.x Repository Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Maven version: 2.0.7 > Java version: 1.4.2_13 > OS name: "windows xp" version: "5.1" arch: "x86" >Reporter: Julien HENRY >Assignee: Carlos Sanchez > Fix For: 2.1 > > > On a simple project, I run: > mvn clean source:jar javadoc:jar repository:bundle-create > As a result in target I get: > artifact-version.jar > artifact-version-bundle.jar > artifact-version-javadoc.jar > artifact-version-sources.jar > But in artifact-version-bundle.jar there are only: > META-INF > pom.xml > LICENSE.txt > artifact-version.jar > artifact-version-sources.jar -- 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
[jira] Created: (MAVENUPLOAD-2198) Please upload simple-4.0.1 to central Maven 2 repo
Please upload simple-4.0.1 to central Maven 2 repo -- Key: MAVENUPLOAD-2198 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2198 Project: Maven Upload Requests Issue Type: Wish Reporter: Gary S. Weaver Attachments: simple-web-4.0.1-bundle.jar, simple-web-4.0.1.jar Simple ( http://www.simpleframework.org/ ) is self described as: "The goal of Simple is to bring the power of simplicity to the world of server side Java. The primary focus of the project is to provide a truly embeddable Java based HTTP engine capable of handling enormous loads. Simple provides a truly asynchronous service model, request completion is driven using an internal, transparent, monitoring system. This allows Simple to vastly outperform most popular Java based servers in a multi-tier environment, as it requires only a very limited number of threads to handle very high quantities of concurrent clients. Simple has consistently out performed both commercial and open source Java Servlet engines and has a fully comprehensive API that is as usable for experienced Java developers as it is for beginners. Best of all, Simple is completely free, and is released under the terms of the GNU Lesser General Public License, LGPL, which ensures its availability for use by open source and proprietary developers alike." Simple is also mentioned here (where I found reference to it): http://java-source.net/open-source/web-servers I think it would make a good addition to the central Maven 2 repository, and I'd consider using it in a project I'm developing. I also mentioned it on the maven users mailing list. I will attempt to contact the developer to inform him of this. Bundle attached. -- 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
[jira] Updated: (MAVENUPLOAD-2197) Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver updated MAVENUPLOAD-2197: Attachment: rupy-0.2.4-bundle-2.jar Oops. The groupId in the first attached bundle included the artifact name, which it shouldn't have to be clean. Fixed, re-bundled, and attached as rupy-0.2.4-bundle-2.jar > Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite > version number) > -- > > Key: MAVENUPLOAD-2197 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2197 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: rupy-0.2.4-bundle-2.jar, rupy-0.2.4-bundle.jar, > rupy-0.2.4.jar > > > Rupy ( http://code.google.com/p/rupy/ ) is self described as: "Weighing less > than 50KB, rupy is probably the smallest Java NIO application server in the > world. Rupy is inherently non-blocking asynchronous, which makes it the ideal > candidate for high concurrency real-time applications pushing dynamic data. > Tested with acme, rupy performs on average ~1500 requests per second. To put > that figure in perspective; acme doesn't use keep-alive, so that means 1500 > unique TCP connections serving dynamic content per second! Thanks to NIO and > an event queue to avoid selector trashing, this figure degrades gracefully > under high concurrency. " > Rupy is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I renamed http.jar in the bundle to rupy-0.2.4.jar to meet convention. It > appears to be a final release, even though is versioned as v0.2.4. > I will attempt to contact the developer to inform him of this. -- 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
[jira] Commented: (MAVENUPLOAD-2198) Please upload simple-4.0.1 to central Maven 2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146868#action_146868 ] Gary S. Weaver commented on MAVENUPLOAD-2198: - Note: response from developer: "Hi, Thanks fine, however there is a slight bug in 4.0.1 which I have just resolved. Should be released by the end of the week. I will ensure to upload this version also. Thanks, Niall" So once he updates it at end of week (or so) I'll rebundle and attach new version to this ticket. > Please upload simple-4.0.1 to central Maven 2 repo > -- > > Key: MAVENUPLOAD-2198 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2198 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: simple-web-4.0.1-bundle.jar, simple-web-4.0.1.jar > > > Simple ( http://www.simpleframework.org/ ) is self described as: "The goal of > Simple is to bring the power of simplicity to the world of server side Java. > The primary focus of the project is to provide a truly embeddable Java based > HTTP engine capable of handling enormous loads. Simple provides a truly > asynchronous service model, request completion is driven using an internal, > transparent, monitoring system. This allows Simple to vastly outperform most > popular Java based servers in a multi-tier environment, as it requires only a > very limited number of threads to handle very high quantities of concurrent > clients. Simple has consistently out performed both commercial and open > source Java Servlet engines and has a fully comprehensive API that is as > usable for experienced Java developers as it is for beginners. Best of all, > Simple is completely free, and is released under the terms of the GNU Lesser > General Public License, LGPL, which ensures its availability for use by open > source and proprietary developers alike." > Simple is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I will attempt to contact the developer to inform him of this. > Bundle attached. -- 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
[jira] Closed: (MAVENUPLOAD-2198) Please upload simple-4.0.1 to central Maven 2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver closed MAVENUPLOAD-2198. --- Resolution: Incomplete Going to close this and open up a new bug for uploading v4.0.2 instead so there won't be any confusion. > Please upload simple-4.0.1 to central Maven 2 repo > -- > > Key: MAVENUPLOAD-2198 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2198 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: simple-web-4.0.1-bundle.jar, simple-web-4.0.1.jar > > > Simple ( http://www.simpleframework.org/ ) is self described as: "The goal of > Simple is to bring the power of simplicity to the world of server side Java. > The primary focus of the project is to provide a truly embeddable Java based > HTTP engine capable of handling enormous loads. Simple provides a truly > asynchronous service model, request completion is driven using an internal, > transparent, monitoring system. This allows Simple to vastly outperform most > popular Java based servers in a multi-tier environment, as it requires only a > very limited number of threads to handle very high quantities of concurrent > clients. Simple has consistently out performed both commercial and open > source Java Servlet engines and has a fully comprehensive API that is as > usable for experienced Java developers as it is for beginners. Best of all, > Simple is completely free, and is released under the terms of the GNU Lesser > General Public License, LGPL, which ensures its availability for use by open > source and proprietary developers alike." > Simple is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I will attempt to contact the developer to inform him of this. > Bundle attached. -- 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
[jira] Updated: (MAVENUPLOAD-2197) Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite version number)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver updated MAVENUPLOAD-2197: Attachment: rupy-0.2.4-bundle-3.jar Fixed and attached as rupy-0.2.4-bundle-3.jar > Please upload rupy-0.2.4 to central Maven 2 repo (is final version despite > version number) > -- > > Key: MAVENUPLOAD-2197 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2197 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: rupy-0.2.4-bundle-2.jar, rupy-0.2.4-bundle-3.jar, > rupy-0.2.4-bundle.jar, rupy-0.2.4.jar > > > Rupy ( http://code.google.com/p/rupy/ ) is self described as: "Weighing less > than 50KB, rupy is probably the smallest Java NIO application server in the > world. Rupy is inherently non-blocking asynchronous, which makes it the ideal > candidate for high concurrency real-time applications pushing dynamic data. > Tested with acme, rupy performs on average ~1500 requests per second. To put > that figure in perspective; acme doesn't use keep-alive, so that means 1500 > unique TCP connections serving dynamic content per second! Thanks to NIO and > an event queue to avoid selector trashing, this figure degrades gracefully > under high concurrency. " > Rupy is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I renamed http.jar in the bundle to rupy-0.2.4.jar to meet convention. It > appears to be a final release, even though is versioned as v0.2.4. > I will attempt to contact the developer to inform him of this. -- 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
[jira] Commented: (MAVENUPLOAD-2228) Upload for Simple Framework
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149555#action_149555 ] Gary S. Weaver commented on MAVENUPLOAD-2228: - Looking forward to seeing this in the central Maven 2 repo. Thanks, Niall! > Upload for Simple Framework > --- > > Key: MAVENUPLOAD-2228 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2228 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Niall Gallagher > Attachments: simple-4.0.4-javadoc.jar, simple-4.0.4-sources.jar, > simple-4.0.4.jar > > > http://www.simpleframework.org/download/simple-4.0.4-bundle.jar > http://www.simpleframework.org/ > http://www.simpleframework.org/doc/javadoc/org/simpleframework/http/Server.html > I'm the developer of Simple, the Simple XML framework is currently in Maven > and I would like to add the main HTTP framework. > Thanks, > Niall -- 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
