Imports of required classes have classname only without package path within the class compiled by maven
The web project composed of several modules can be deployed to the
application server (WAS 8.5.5) and runs as expected, when built within
eclipse (juno sp2) by the eclipse compiler. The same project built with
maven, either through the m2e-wtp plugin or with mvn clean install from
the command line, can not be run on the AppServer.
Maven build worked too, but does not anymore for unknown reason. No
changes of configuration or programs but update of m2e-wtp.
All required configuration files bundled within the resulting project.ear
are correct and identical to the version compiled with eclipse.
On analyzing the issue it turned out, some classes compiled by maven have
defective import lists!
For instance:
A *.class file decompiled with jd has the following import list:
import DocumentId;
import DocumentKind;
import IProject;
import IRequirement;
import java.io.Serializable;
import java.util.List;
import java.util.Locale;
import java.util.Map;
import java.util.logging.Logger;
import javax.faces.model.SelectItem;
We see, the list is truncated, and some imports have the class name only,
but no package information.
If we look at the same decompiled class file, but the outcome from the
eclipse compiler, the list look like:
import ch.commcity.monterosa.common.reports.DocumentId;
import ch.commcity.monterosa.common.reports.DocumentKind;
import ch.commcity.monterosa.ejb.IProject;
import ch.commcity.monterosa.ejb.IRequirement;
import java.io.IOException;
import java.io.Serializable;
import java.security.InvalidParameterException;
import java.security.Principal;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Collections;
import java.util.HashMap;
import java.util.List;
import java.util.Locale;
import java.util.Map;
import java.util.ResourceBundle;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.faces.application.Application;
import javax.faces.application.ConfigurableNavigationHandler;
import javax.faces.application.FacesMessage;
import javax.faces.context.ExternalContext;
import javax.faces.context.FacesContext;
import javax.faces.model.SelectItem;
First, the latter list is longer and second the import DocumentId for
instance includes the full package path!
As the import list is defective, no surprise all methods look like the
following example:
int getFrom()
{
throw new Error(Unresolved compilation problem: \n);
}
instead of:
int getFrom() {
return this.from;
}
which is neither very sophisticated, but does was is expected to be done.
Question:
All dependencies declarations within the poms are the same as before. May
a missing declaration be the origin of the problem, which before had no
effect?
What else? I must say I had the same problem in February of this year, But
without any conscious change (I suspect after update to sp2 of juno) it
worked suddenly as now it stopped to work, maybe due to the m2e-wtp
update!
The poms are unchanged and within the Kepler IDE environment maven
compiles the code as expected. The only differences are some parts proper
to the glassfish 3.1.2 Appserver and for the Mojarra version of JSF in
turn of MyFaces used by WebSphere.
Any hint or suggestion is welcome.
Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
Hi,
i am very new to maven. I am trying to import hadoop source code into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
Highlights don't get get through when sendig from Nabble.
But the error message is saying that you are using Maven 2.2.1, but you
need to use Maven 3.0.2 or greater. I strongly suggest you use Maven 3.0.4
or 3.0.5.
/Anders
On Fri, Oct 25, 2013 at 8:46 AM, rushikeshgarad...@gmail.com
rushikeshgarad...@gmail.com wrote:
Hi,
i am very new to maven. I am trying to import hadoop source code into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
The people who write the software you are trying to build have decreed that
you need to use a recent version of Maven in order to build correctly. They
have defined an enforcer rule to enforce their minimum maven version
requirement. The enforcer rule has kicked in and failed the build early
because you are using maven version 2.2.1 and the allowed range is [3.0.2,)
Maven has a version range syntax. briefly
[x] means only version x and no other version
[x,y] means any version =x and =y
[x,y) means any version =x and y
(x,y] means any version x and =y
(x,y) means any version x and y
(,x] means any version =x
[x,) means any version =x
(,x) means any version x
(x,) means any version x
HTH
On 25 October 2013 07:46, rushikeshgarad...@gmail.com
rushikeshgarad...@gmail.com wrote:
Hi,
i am very new to maven. I am trying to import hadoop source code into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
FTR, here is the standard requires I add to most of my projects:
requireMavenVersion
version(,2.1.0),(2.1.0,2.2.0),(2.2.0,)/version
messageMaven 2.1.0 and 2.2.0 produce incorrect GPG
signatures and checksums respectively.
/message
/requireMavenVersion
requireMavenVersion
version(,3.0),[3.0.4,)/version
messageMaven 3.0 through 3.0.3 inclusive do not pass
correct settings.xml to Maven Release
Plugin.
/message
/requireMavenVersion
Hadoop are not as forgiving as me it would seem
On 25 October 2013 11:23, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
The people who write the software you are trying to build have decreed
that you need to use a recent version of Maven in order to build correctly.
They have defined an enforcer rule to enforce their minimum maven version
requirement. The enforcer rule has kicked in and failed the build early
because you are using maven version 2.2.1 and the allowed range is [3.0.2,)
Maven has a version range syntax. briefly
[x] means only version x and no other version
[x,y] means any version =x and =y
[x,y) means any version =x and y
(x,y] means any version x and =y
(x,y) means any version x and y
(,x] means any version =x
[x,) means any version =x
(,x) means any version x
(x,) means any version x
HTH
On 25 October 2013 07:46, rushikeshgarad...@gmail.com
rushikeshgarad...@gmail.com wrote:
Hi,
i am very new to maven. I am trying to import hadoop source code into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
On 25 October 2013 11:26, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
FTR, here is the standard requires I add to most of my projects:
requireMavenVersion
version(,2.1.0),(2.1.0,2.2.0),(2.2.0,)/version
This range lets through any maven version before 2.1.0.
We have not issued a patch version of 2.1.0 to fix the GPG signature issue,
but if we did, it will be innocent until proven guilty
2.2.0 is not allowed, but everything after it is
messageMaven 2.1.0 and 2.2.0 produce incorrect GPG
signatures and checksums respectively.
/message
/requireMavenVersion
requireMavenVersion
version(,3.0),[3.0.4,)/version
Everything prior to 3.0 passes the settings.xml correctly
3.0.4 contains the fix and thus everything after will have the fix, or at
least is innocent until proven guilty
messageMaven 3.0 through 3.0.3 inclusive do not pass
correct settings.xml to Maven Release
Plugin.
/message
/requireMavenVersion
Hadoop are not as forgiving as me it would seem
I could give one single consolidated range, but then you don't get a nice
message explaining why the specific versions are banned.
On 25 October 2013 11:23, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The people who write the software you are trying to build have decreed
that you need to use a recent version of Maven in order to build correctly.
They have defined an enforcer rule to enforce their minimum maven version
requirement. The enforcer rule has kicked in and failed the build early
because you are using maven version 2.2.1 and the allowed range is [3.0.2,)
Maven has a version range syntax. briefly
[x] means only version x and no other version
[x,y] means any version =x and =y
[x,y) means any version =x and y
(x,y] means any version x and =y
(x,y) means any version x and y
(,x] means any version =x
[x,) means any version =x
(,x) means any version x
(x,) means any version x
HTH
On 25 October 2013 07:46, rushikeshgarad...@gmail.com
rushikeshgarad...@gmail.com wrote:
Hi,
i am very new to maven. I am trying to import hadoop source code
into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i
have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Imports of required classes have classname only without package path within the class compiled by maven
Maven build worked too, but does not anymore for unknown reason. No changes of configuration or programs but update of m2e-wtp. This list does not support m2e. You'll need to ask this question on the appropriate Eclipse list. We can help you sort out why command line Maven is not working as it should. All required configuration files bundled within the resulting project.ear are correct and identical to the version compiled with eclipse. On analyzing the issue it turned out, some classes compiled by maven have defective import lists! ... We see, the list is truncated, and some imports have the class name only, but no package information. If we look at the same decompiled class file, but the outcome from the eclipse compiler, the list look like: Maven (command line) simply calls out to the JDK installed on your system. You can use mvn -X to see the actual command that Maven uses to call javac. If you are experiencing problems with the output of Maven's compilation process, your real complaint is with the JDK javac itself, not Maven. I trust that you realize that Eclipse has and uses its own compiler, so I would expect that you might see some different results when analyzing class files produced by the 2 compilers. Is it possible that javac simply reduced your import list because a) they were not all being used or b) it swapped out the import and replaced the short name for the class with the fully-qualified name? Did you look at the rest of the source code that came out of jd? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Adding to Books on Maven?
How does one get added to the list of available Maven publications on the site (http://maven.apache.org/articles.html)? - Author, Getting Started with Apache Maven http://www.packtpub.com/getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!
Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Can somebody please check the issue posted above and provide a fix if possible. I am completely stuck due to this and management now wants me to revert the mvn deploy to mvn install. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773827.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Can you explain how you are copying the artifacts currently? You say that your dependencies are being packaged with a timestamp. How are you doing this? And then you say that you are copying the flex artifact with a plugin. What plugin is that? I think that you need to explain a bit more what is going on, here. - Russ On Oct 18, 2013, at 10:45 AM, sahil_tech sahilaggarwal1...@gmail.com wrote: Hi, I am building snapshots artifacts in CI tool Hudson and deploying them into nexus using distribution management in my pom.xml and Snapshot is getting replaced by timestamp in final artifact name on uploading into nexus because non-unique snapshots are no more valid in maven 3, that is fine. Also, on looking for dependency in nexus repo, it always fetch the latest snapshot artifact as I can see the time stamp and build number in debug logs. But, now the problem that I am facing. 1. in WEB-INF/lib of war file.. dependencies are packaging with timestamp. 2. In my project, I am using plugin to copy flex code into my war file but that again copy the flex artifact with timestamp. But, I have hard coded the artifact name in my jsp as gui-flex-14.0-SNAPHOT.swc. Due to this I am getting blank screen. So, please let me know is there any way to convert unique snapshot artifacts into non-unique on downloading from nexus. In simple words, I am proposing that the Maven client download a snapshot artifact named A-1.0.0-20110302.160157-17.jar and then rename it to A-1.0.0-SNAPSHOT.jar when it stores the file locally. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Author, Getting Started with Apache Maven http://www.packtpub.com/getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!
Re: Trying to understand how maven finds source
On Thu, Oct 24, 2013 at 10:34:39PM -0400, Ron Wheeler wrote: Eclipse/STS from the Spring guys (VMWare now) is an Eclipse IDE with all of the plug-ins that you need to develop Java (and more). We started with pure Eclipse but spent so much time fixing up the plug-ins with each new version that it affected our productivity. Once we found the Spring Tool Suite (Eclipse with all the right plug-ins) we were in good shape - 1 download and we were back up and coding in a few minutes. I have never used NetBeans so I have no comment about how it helps with the original problem(source code location). NetBeans helps quite a lot. I've been shamefully spoiled by it and tend to use it even just to browse code when I have no intent to develop it. I've used Eclipse (not STS though) and was happy to see the back of it after losing too much time to plugins-disease. I hear that IntelliJ is good with Maven projects too. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature
Re: Trying to understand how maven finds source
Maybe it is mustard after the mail (as the Dutch call it. ;) ), but here is a nice article about the standard directory layout of Maven: http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Hth, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Thu, Oct 24, 2013 at 10:04 PM, Robert Dailey rcdailey.li...@gmail.comwrote: Hey everyone, I'm trying to understand something basic, I haven't been able to find the answer through Google surprisingly (maybe my searching abilities suck today). How is it that Maven is able to find source code to compile? What I would expect is the pom.xml to refer to some *.java path (something like sourcesrc/main/java/*/source), but I don't see anything like that. How does maven know what java source code to compile? Thanks in advance for any help. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Could you explain what you mean by Unique and non-Unique? From: sahil_tech [sahilaggarwal1...@gmail.com] Sent: Friday, October 25, 2013 8:55 AM To: users@maven.apache.org Subject: Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus Can somebody please check the issue posted above and provide a fix if possible. I am completely stuck due to this and management now wants me to revert the mvn deploy to mvn install. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773827.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Actually this is quite surprising. I would expect the timestamp to be not visible to the end user. You build/deploy a -SNAPSHOT version , you ask for a -SNAPSHOT version, you get a -SNAPSHOT in your war. Internally maven/nexus may use real timestamp but this is not supposed to be visible. Whatever you are using to do this must not do it correctly. On Fri, Oct 18, 2013 at 4:45 PM, sahil_tech sahilaggarwal1...@gmail.comwrote: Hi, I am building snapshots artifacts in CI tool Hudson and deploying them into nexus using distribution management in my pom.xml and Snapshot is getting replaced by timestamp in final artifact name on uploading into nexus because non-unique snapshots are no more valid in maven 3, that is fine. Also, on looking for dependency in nexus repo, it always fetch the latest snapshot artifact as I can see the time stamp and build number in debug logs. But, now the problem that I am facing. 1. in WEB-INF/lib of war file.. dependencies are packaging with timestamp. 2. In my project, I am using plugin to copy flex code into my war file but that again copy the flex artifact with timestamp. But, I have hard coded the artifact name in my jsp as gui-flex-14.0-SNAPHOT.swc. Due to this I am getting blank screen. So, please let me know is there any way to convert unique snapshot artifacts into non-unique on downloading from nexus. In simple words, I am proposing that the Maven client download a snapshot artifact named A-1.0.0-20110302.160157-17.jar and then rename it to A-1.0.0-SNAPSHOT.jar when it stores the file locally. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Adrien Rivard
Re: Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,)
Thank You Sir,
i was there with maven2...now i have installed 3.X version.
Thank you for help
On Fri, Oct 25, 2013 at 4:01 PM, stephenconnolly [via Maven]
ml-node+s40175n577380...@n5.nabble.com wrote:
On 25 October 2013 11:26, Stephen Connolly
[hidden email] http://user/SendEmail.jtp?type=nodenode=5773808i=0wrote:
FTR, here is the standard requires I add to most of my projects:
requireMavenVersion
version(,2.1.0),(2.1.0,2.2.0),(2.2.0,)/version
This range lets through any maven version before 2.1.0.
We have not issued a patch version of 2.1.0 to fix the GPG signature
issue,
but if we did, it will be innocent until proven guilty
2.2.0 is not allowed, but everything after it is
messageMaven 2.1.0 and 2.2.0 produce incorrect GPG
signatures and checksums respectively.
/message
/requireMavenVersion
requireMavenVersion
version(,3.0),[3.0.4,)/version
Everything prior to 3.0 passes the settings.xml correctly
3.0.4 contains the fix and thus everything after will have the fix, or at
least is innocent until proven guilty
messageMaven 3.0 through 3.0.3 inclusive do not
pass
correct settings.xml to Maven Release
Plugin.
/message
/requireMavenVersion
Hadoop are not as forgiving as me it would seem
I could give one single consolidated range, but then you don't get a nice
message explaining why the specific versions are banned.
On 25 October 2013 11:23, Stephen Connolly
[hidden email] http://user/SendEmail.jtp?type=nodenode=5773808i=1
wrote:
The people who write the software you are trying to build have decreed
that you need to use a recent version of Maven in order to build
correctly.
They have defined an enforcer rule to enforce their minimum maven
version
requirement. The enforcer rule has kicked in and failed the build early
because you are using maven version 2.2.1 and the allowed range is
[3.0.2,)
Maven has a version range syntax. briefly
[x] means only version x and no other version
[x,y] means any version =x and =y
[x,y) means any version =x and y
(x,y] means any version x and =y
(x,y) means any version x and y
(,x] means any version =x
[x,) means any version =x
(,x) means any version x
(x,) means any version x
HTH
On 25 October 2013 07:46, [hidden
email]http://user/SendEmail.jtp?type=nodenode=5773808i=2
[hidden email] http://user/SendEmail.jtp?type=nodenode=5773808i=3
wrote:
Hi,
i am very new to maven. I am trying to import hadoop source code
into
eclipse. and for this i followed this link:
http://wiki.apache.org/hadoop/EclipseEnvironment
in this there are 2 mvn commands:
$ mvn install -DskipTests
$ mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
during both command execution i came across following error
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
*Detected Maven Version: 2.2.1 is not in the allowed range [3.0.2,).*
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific
messages
explaining why the rule failed.
Highlighted one is main area of interest which i didn't understood.(i
have
installed maven2) Please can u help me in solving above query.
Thank You
--
View this message in context:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=5773808i=4
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=5773808i=5
--
If you reply to this email, your message will be added to the discussion
below:
http://maven.40175.n5.nabble.com/Detected-Maven-Version-2-2-1-is-not-in-the-allowed-range-3-0-2-tp5773798p5773808.html
To unsubscribe from Detected Maven Version: 2.2.1 is not in the allowed
range [3.0.2,), click
herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5773798code=cnVzaGlrZXNoZ2FyYWRhZGVAZ21haWwuY29tfDU3NzM3OTh8MjAyMDA0MjI0NA==
.
Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Hi Russell, I am using maven version 3 and I have configured the maven jobs in Hudson (mvn clean deploy) to deploy the unique snapshots artifacts into a nexus hosted repository and for that I have configured distribution management tag in project parent pom.xml. I am using maven-war-plugin to collect all artifact dependencies, classes and resources of the web application and packaging them into a web application archive. But, now while packaging I am getting snapshot dependencies with timestamp in WEB-INF/lib of war file. To copy the flex artifacts (swf artifact) into my gui war project, I am using org.sonatype.flexmojos:flexmojos-maven-plugin: copy-flex-resources during process-resource phase. But, it again copying flex artifacts with timestamp. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773845.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Hi Amir, Non-unique snapshot artifacts - without timestamp. unique snapshot artifact - with timestamp. Maven 3 only support unique snapshot. In maven 2, we set the uniqueversionfalse/uniqueversion to deploy the non-unique snapshot artifacts. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773846.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Hi Adrein, Maven is downloading snapshot dependencies with timestamp into my local repository. I have timestamp versions of snapshot dependency in my local repository and the files are getting copied with their standard names. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773854.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven shade plugin: Retaining origin file timestamps
We could remove clj files from the jar altogether. However, the problem is we don't know if all the clojure dependencies are AOT compiled. So, some of the clojure files should be compiled on the fly. The problem is when dynamically compiling clojure files whose class files already exist in the jar. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-shade-plugin-Retaining-origin-file-timestamps-tp5773664p5773855.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven shade plugin: Retaining origin file timestamps
We could remove clj files from the jar altogether. However, the problem is we don't know if all the clojure dependencies are AOT compiled. So, some of the clojure files should be compiled on the fly. The problem is when dynamically compiling clojure files whose class files already exist in the jar. Well, I see this as an opportunity to do that work today. If you just figure this out now, you will have a short list of files to filter out during the packaging step. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
