On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
Hi,
I'm looking for a way to attach an extra generated artifact to a project
so it's installed and deployed in the standard project lifecycle, how
can i do this? Do i need to write a mojo or can i just add this as part
of the pom config?
you are not understanding lifecycles!
mvn install means run every stage in the lifecycle upto and including
install
mvn deploy means run every stage in the lifecycle upto and including
deploy
mvn install deploy means run every stage in the lifecycle upto and
including install, then run every
If you send us your configuration we might be able to help you...
Also make sure that you are using 2.0-beta-3.
Savita_p_m wrote:
Hi Adam,
did u fix this problem? even I am facing the same problem. Can you please
let me know how did u resolve it,
I am getting the following error when I try
Hi all,
this is the output of ant -v.
As you can see, it cannot download the artefact
com.ibm.isov.grdm:grdm-parent:pom:2.0.1.3-SNAPSHOT which is the parent of
the pom file I'm loading with ant. The artefact is on the repository
configured in C:\Documents and
Even if I move the configuration of the repository to the pom I'm loading
with ant it cannot download the parent. It always says:
[artifact:pom] Using remote repositories:
- id=central, url=http://repo1.maven.org/maven2, releases=enabled,
snapshots=disabled
On Feb 2, 2008 12:49 PM, Thomas
ok, I see.
[artifact:pom] Using remote repositories:
- id=central, url=http://repo1.maven.org/maven2, releases=enabled,
snapshots=disabled
The repository defined in your settings.xml is not used, since it is defined
in a profile.
This is a known limitation: profiles are not supported yet,
But even if I copy the repository configuration from the settings.xml to the
pom it's not working. And in the pom it's not defined in a profile.
On Feb 2, 2008 1:07 PM, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
ok, I see.
[artifact:pom] Using remote repositories:
- id=central,
Hi all,
I know it is a well known issue but I am really stuck!
I am in the process of migrating some Java applications build system to
Maven 2. developers need to build the applications for different environment
like local/staging/QA/prod. in the old build system we have one property
file
ok, this one looks like a bug
Please file a Jira issue.
Le samedi 02 février 2008, Thomas Tardy a écrit :
But even if I copy the repository configuration from the settings.xml to
the pom it's not working. And in the pom it's not defined in a profile.
On Feb 2, 2008 1:07 PM, Hervé BOUTEMY
Do you have any information about the
http://jira.codehaus.org/browse/MANTTASKS-35. When will it be implemented?
On Feb 2, 2008 1:07 PM, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
ok, I see.
[artifact:pom] Using remote repositories:
- id=central, url=http://repo1.maven.org/maven2,
last time I worked on it was just before 2.0.8: I started to work on it, and
it totally broke dependencies sorting in MANTTASKS, I had to revert for the
release.
I'm actually working on this sorting issue to be sure it won't break anything
when I'll try again to add profile feature in
Put the properties themselves inside the profiles. Or, use filtering
with various named filters eg qa.filter and specify the proper filter
to use in your profile.
Wayne
On 2/1/08, Arash Bizhan zadeh [EMAIL PROTECTED] wrote:
Hi all,
I know it is a well known issue but I am really stuck!
I am
Two more things to check:
1. The debug output shows that you are using 2.0-beta-2:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-changes-plugin:2.0-beta-2:announcement-generate'
--
Please make sure that you have configured the version 2.0-beta-3 correctly.
2. Is the URL really
We are using
http://www.jfrog.org/sites/jade-plugins/latest/jade-plugin-parent/jade-build-plugin-parent/jade-multijar-plugin/index.html
Erez.
On Feb 2, 2008 10:12 AM, simon [EMAIL PROTECTED] wrote:
On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
Hi,
I'm looking for a way to attach an
cool, thanks for the clarification :)
Stephen Connolly wrote:
you are not understanding lifecycles!
mvn install means run every stage in the lifecycle upto and including
install
mvn deploy means run every stage in the lifecycle upto and including
deploy
mvn install deploy means run every
great - thanks for the links
cam
simon wrote:
On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
Hi,
I'm looking for a way to attach an extra generated artifact to a project
so it's installed and deployed in the standard project lifecycle, how
can i do this? Do i need to write a mojo or can
hi,
i was wondering if there's any way to do simple scripting in a pom? the
specific case i'm trying to solve is to generate a database schema name
based on the version of the project. If my project version is
0.1-SNAPSHOT i'd like the database to be called 0_1_snapshot since '.'
and '-' are
hi arash,
as far as i am aware (i've only been using maven for about 6 months so
i'm no real authority on it) but the easiest way to accomplish is to
have the properties defined in the environment profiles, eg in your main
pom:
profile
idbuild/id
activation
property
You could probably achieve this with a little Beanshell or Groovy
plugin, or Java for that matter. You'd need to bind the property back
to the MavenProject so it would propagate throughout your build.
Wayne
On 2/2/08, Cam [EMAIL PROTECTED] wrote:
hi,
i was wondering if there's any way to do
We have a maven version for our incubating project which looks like:
2.3.0.incubating-SNAPSHOT
The dot before incubating is there to make the format fit the Eclipse
syntax of major.minor.micro.qualifier
When eclipse:eclipse updates the MANIFEST.MF, it changes this version to:
20 matches
Mail list logo
