Hi everyone
I have a small problem executing my JUnit test which depend on some test
files (xml and plaintext documents). Whenever I run mvn test surefire
compiles all JUnit Testclasses to target/test-classes but my test files
don´t get copied to target/test-classes and therefore my JUnit tests
Niranjan Deshpande schrieb:
Tim i indeed wht u suggested
tasks
ant antfile/
/tasks
but the build xmls just dont seem to to reached..
It's working for me with this test project:
.
|-- pom.xml
`-- src
`-- main
|-- antscripts
| |-- antscript1.xml
This might be easier in the short run, but consider what happens when
you do a release - your repo definitions are forever stuck in the
released POM and so would force you to keep running your internal repo
at that specific address forever (or force users to specify some
mirror settings if the
Hi Tim,
Tim Kettler wrote:
Just put the files under src/test/resources and maven will copy them to
the correct destination, exactly like it's doing it for production files
under src/main/resources.
Thank you very much. This solved my problem.
Best regards
Silvio
--
View this
I wanted to see if others have addressed this requirement before and
what approaches they have taken:
We have certain artifacts which need to be built for multiple platforms.
For example, we may have j2ee artifacts that get deployed to Websphere 6
and Websphere 6.1. We use profiles to setup the
What about having a maven project for each platform using the same
parent pom, rather than architecting the solution on profiles?
/Johan
6 jun 2008 kl. 09.47 Timothy Reilly [EMAIL PROTECTED] skrev:
I wanted to see if others have addressed this requirement before and
what approaches they
We use jaxb and I must confess that was not easy to set up our
environment. Our pom has the dependencies listed below. Let me know if
that works for you.
Regards,
Javier
dependency
groupIdjavax.xml.bind/groupId
artifactIdjaxb-api/artifactId
Tim thanks
I am finally able to reach the ant build file. I have moved the
configuration back into the exections as said by you, as I want the
pluging to run when my code is compiled, and dont want to run it stand
alone.
but the problem is the plugin does not run when i say mvn install or mvn
Hi,
Back in the days there used to be a piece of information on specifying a new
package on the maven web site. I found a backup at [1]. Also at [2] there is
issue with patch which adds a new packaging. So maybe you have to patch a
custom maven installation to provide your package type.
Hth,
Are you using your own custom checks or provide a custom
packagenames.xml file? In that case see this page:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/custom-developed-checkstyle.html
Julien Simon wrote:
Thanks for the answer. So, I tried maven-checkstyle-plugin 2.2 and
I think you need to accept the fingerprint for the server once. Try
connecting to the server from the command line first:
plink [EMAIL PROTECTED]
Mick Knutson wrote:
I keep getting this error:
*[INFO] [site:deploy]
The authenticity of host '208.96.48.200' can't be established.
RSA key
Specify a release version (2.0.1) for project-info-reports-plugin.
Mick Knutson wrote:
Yes, but I do not see a described resolution.
On Thu, Jun 5, 2008 at 9:34 AM, Tim Kettler [EMAIL PROTECTED] wrote:
Hi,
Mick Knutson schrieb:
I have the following for my reports declaration:
...
Then I
Many thanks for the links, Nick,
Unfortunately the second link does not work. Could you possibly resend?
Many thanks.
--
Regards
Andrew
Hi,
Back in the days there used to be a piece of information on specifying a new
package on the maven web site. I found a backup at [1]. Also at [2]
Hi,
i'd like to know if it's possible to attach an artifact from an Ant mojo. I
have seen archived posts
in the mailing list that suggest usage of the build helper mojo.
But, is it possible to use the build helper from my Ant mojo ? I mean from
my understanding, the build helper
plugin has to be
I am trying to generate a .properties file using javadocs in a java source
file, and i am using ant's javadoc task to do this.
but i am getting this error when i run the antrun plugin
generate.appcodes:
[javadoc] Generating Javadoc
[javadoc] Javadoc execution
[javadoc] javadoc: Cannot find
Hi,
I'm currently editing the PLEXUS\components file:
[code]
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintspring/role-hint
implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation
configuration
It also works as a shorter version:
https://jira.codehaus.org/browse/MNG-3343
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: Andrew Madu [mailto:[EMAIL PROTECTED]
Sent: Fri 6/6/2008 14:22
To: Maven Users List
What you're seeing there is which plugin with which goal to run. As far as I
know there is no plugin which creates such .spring files. Are they any
special files?
One solution I see is to specify the assembly plugin there and provide a
default configuration in your company's parent pom. (Sort
Hi all,
I would like to activate profile which is placed in super pom for using
it in child project.
The reason:
I would like to use common properties but depends on profile in many
child projects.
Sample situation:
- super pom:
project ...
groupIdmyGroupId/groupId
I'm still confused on why it wouldn't be a good idea to simply put the
company repository info in a parent pom that all company projects would use?
This seems a lot cleaner and easier to setup and maintain...
1) If it's in a parent pom and you need to change repository urls someone
can update the
Hi Nick,
the .spring archive is nothing special, just a means by which spring
beans can be exposed via JNDI. The file will contain a class directory
structure with a bean descriptor file located in the META-INF directory.
The following document explains the .spring requirement:
I'm using custom checks, I followed the procedure described on the web link
you gave me. Everything now works correctly.
Maybe I'm wrong but I think there's a mistake in this documentation: in the
pom.xml example, dependencies containing custom developed checks are placed
in the build extensions
Then the assembly plugin would be your friend.
http://maven.apache.org/plugins/maven-assembly-plugin/
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: Andrew Madu [mailto:[EMAIL PROTECTED]
Sent: Fri 6/6/2008
If your parent pom is always a snapshot, your option 1) will probably
work, but then you will sacrifice build reproducibility (old projects
built and released with one snapshot version could in the future
suddenly be built with a new parent pom - anything which might change
a released build is not
!-- BEG COMMENT ===
add this debug Ant target to your depends= to expose the properties in play
END COMMENT === --
target name=display.properties.tgt description=display project
properties.
echoproperties
Hi
You probably still have the old version of that page cached in your
browser. A new corrected version of the page was deployed on June 4.
Check that the publish date matches.
You are correct that your checks should be added as a plugin dependency.
Julien Simon wrote:
I'm using custom
I got this when I ran your debug script. Error executing ant tasks
_
Embedded error: The following error occurred while executing this line:
/home/apli/APPWeb/src/main/build/generate/generate-appcodes.xml:37:
I know - yet another survey type email. After the last one, I could
sleep better at night knowing we're not barking up some strange,
difficult tree with the config file question.
So the next question is focused on those using Cruise Control and maven
2.
Initially, if a large product was
Hi Nick,
many thanks for the link.
Out of interest where exactly is the ArchiveManager located?! Also,
would I be correct in assuming that the assembly descriptor xml file is
situated as follows?:
myproject\src\assemble\mydescriptor.xml
Many thanks in advance.
--
Regards
Andrew
Then
of course..echoproperties adds dependency..to another ant component.
here is segment of my ugly pom.xml
[snip]
!-- = --
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepre-site/phase
The Mojo team is pleased to announce the release of the JavaCC Maven Plugin
version 2.4.1.
http://mojo.codehaus.org/javacc-maven-plugin/
This maintenance release fixes bugs preventing the invocation of JTB and
JJDoc on systems that have spaces in their local repo path which is common
on Windows
On Fri, Jun 6, 2008 at 12:34 PM, EJ Ciramella [EMAIL PROTECTED]
wrote:
When it comes down to release time, how are people migrating from
snapshots to releases? Our release numbering scheme has always been in
a major.minor.patch.build-number format. Toward the end of a release
cycle, we
It works, but in our case, we tend to spin multiple builds hoping to release
each candidate (as many as we can squeeze into a day sometimes).
What I don't want to do is move from a highly automated process to one that
requires command line intervention.
-Original Message-
From:
I already wrote to ask about feedback how to organize a project (thanks for
the responses so far), now another question:
Let's assume we have a project like this:
myproject -
EAR-module1
EAR-module2
plugins
plugin-module1
plugin-module2
Now I feel like I'm probably missing something, but you do want to give some
kind of command to release the project, don't you? Releasing a properly
maintained build with the release plugin doesn't require command line
intervention, it can be just another build target on your continuous
so whts wrong in my case?
On Fri, Jun 6, 2008 at 7:31 PM, Sean Hennessy [EMAIL PROTECTED]
wrote:
of course..echoproperties adds dependency..to another ant component.
here is segment of my ugly pom.xml
[snip]
!-- = --
plugin
I have provided sample segments from a working pom.xml and build.xml for your
reference. One instruments ant echoproperties to help diagnose/debug the
classpath and other properties passed along from maven.
Sorry there is a limit to amount of time can spend on wht wrong.
Sean
-Original
37 matches
Mail list logo