Hello. I have worked with 1.0.3 for some time, and after moving to the
newer versions, I have some questions.
What is the fresh build option?
What is the release option?
I was successfully able to install 1.1-alpha-1, and I saw an issue where
I tried to build the group with all the modules,
On 06/08/07, Morgovsky, Alexander (US - Glen Mills)
[EMAIL PROTECTED] wrote:
What is the fresh build option?
Clean check out from SCM
What is the release option?
Uses the Maven release plugin's technology to do a web based release
from SCM (tag, build, update POMs).
I was successfully able
Both could be bugs, though it's a bit hard to tell from the
information you've given. If you can come up with some reproducible
steps we can see, and put them in JIRA, we'll certainly look into it.
On 06/08/07, Morgovsky, Alexander (US - Glen Mills)
[EMAIL PROTECTED] wrote:
Yes, I expected the
That is fine. Thank you.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 05, 2007 9:00 PM
To: continuum-users@maven.apache.org
Subject: Re: 1.1-alpha-beta questions
Both could be bugs, though it's a bit hard to tell from the
information you've
Have a look at this post:
http://www.nabble.com/forum/ViewPost.jtp?post=8838380framed=yskin=177
Paul Spencer-3 wrote:
Maven 2.0.4
I need to include the build time to a properties file. Using resource
filtering, I am setting the version number, but I have not found the
property name,
That's exactly what M2 needs - would you consider releasing your mojo? I'd
love to try using.
IMO this should be apart of the m2 deploy goal.
The problem with Mavin buildnumber plugin, is that it isn't synced with the
build number repository.
Artamonov, Juri wrote:
The thing is that I don't
We have a one-time-use prebuild.sh script to create 2 databases (not the
tables): a normal one and a test one.
Our integration tests are done in spring, which:
1) Boots hibernate-jpa, which does a hbm2ddl=create to create the tables
2) Fires DBunit to create testdata in that database.
Our normal
Hi,
We are currently stuck with the approach of building an EAR file using the
ATG modules to be deployed i n JBoss.
We have defined the following plugins
PMD, JUnit
Now for packaging the ear, ATG provides a assember utility called
runassember.bat which identfies the ATG dependent modules
Are they transitive Maven dependencies? If they are, you can exclude them out
in your pom.xml.
To see which dependency brings these transitive dependencies, try maven -X
and study the dependency tree which maven prints to console.
--
View this message in context:
If I have an artifact of version a.b.c.0 in my local repository, and
someone uploads a newer artifact with version a.b.c.0 to the remote
repository, will my dependent project check if there is a newer version
of artifact a.b.c.0 in all of the repositories compared to that in my
local repository,
If its a SNAPSHOT, then it will look. Otherwise, it will not.
In this case, it sounds like it is not a SNAPSHOT, therefore it will
not look for updates. For Maven to work properly, released versions
must *not* change. If you have files that can/will change, you must
call them SNAPSHOTs.
Wayne
Hi there,
Pom.xml allows you to override final name of the artifact that gets
generated. However, this final name doesn't get carried through when you
deploy to the repository.
I.e., if you have
/myproject/common/library/pom.xml
and say you override final name as myproject-common-library,
It is critical that an artifact with version a.b.c.0 never change
irregardless of what repository it is located in. A released artifact
is static, that is, it is never updated.
It sounds like you want to use SNAPSHOTS which are non-released
development artifact versions. SNAPSHOTS can be
Hi Lara,
I don't think it's possible to specify the descriptors from the command
line as it seems to be not supported by the assembly plugin.
Maybe you could try using profiles [1] to separate the different types
of descriptors (e.g. different plugin config in each profile) for what
you want
14 matches
Mail list logo
