Hi,
The Mojo team is pleased to announce the release of the
chronos-jmeter-maven-plugin and chronos-report-maven-plugin version 1.0.
Chronos enables You to test performance via JMeter, validate that relevant
performance goals have been met, and create nice
visualizations of the latest and
Hello guys,
How can I mavenize a project that uses older versions of EJB like 1.0 or
2.0. I know the plugin does support EJB 2.0+ but it has limited
capabilities. How did people work around this issue. I am sure there must be
a lot of projects that used EJB 2.0 at least if not 1.0 as Maven has
Hi Dennis,
On Mon, Apr 23, 2012 at 9:54 PM, Dennis Lundberg denn...@apache.org wrote:
There are some wrong urls in the pom.xml files, namely in the scm
section.
(I am not sure what impact of this is). It is about:
-the pom.xml in the project root -- tag seems incorrect.
Not sure what
On 24 April 2012 03:02, Andrew Hughes ahhug...@gmail.com wrote:
OK, I found a way to confirm...
activeProfiles are always active Exactly what I wanted as documented
:)
However, the problem persisted... until...
I noticed that builds on the command line worked fine, as did 'install'
Are you seriously still using EJB-1.0? The crap which instantly caused lots of
people puking back in 1999?
I'm aware that a few poor developers still need to clean up the mess in old
projects, but is there even a supported container for those things?
I think EJB-3.0 got introduced in early
And in the interests of keeping ASF vendor neutral,
There are at leaste three repository managers equally capable of providing
95% of what people need (they disagree on the remaining 5% either being
needed or how to solve)
In alphabetical order, so as not to imply any preference:
Archivia by
I know this is an old thread, but for the lurkers of the internets, I might
post a possible answer. In stead of using family as the identifier, one
could use name - either in stead of or in addition to family.
The following should thus be an unambigious activation
activation
os
Hi
The current EAR file only has the first three lines info. How can I add the
next four lines in BOLD? I am using a parent POM which is not created by me.
Thanks
Jirong
Manifest-Version: 1.0
DeployVersion: 7.0.0.0
Created-By: 1.5.0 (IBM Corporation)
*Implementation-Vendor: NBFG
Built-By: NBFG
The current EAR file only has the first three lines info. How can I add the
next four lines in BOLD? I am using a parent POM which is not created by me.
Google for maven manifest.mf leads me to:
http://maven.apache.org/guides/mini/guide-manifest.html
With a link to:
Hi,
I have defined a Parent POM to use the latest versions of Spring Integration
and Spring Data projects
In the Web Module (that inherits from the parent POM), the effective POM
shows a different older version. I thought this could be because of Spring
Projects and their dependency. Later, when
In the Web Module (that inherits from the parent POM), the effective POM
shows a different older version. I thought this could be because of Spring
Projects and their dependency. Later, when I copied the POM entries from
Parent and pasted in the Web Module's POM, I got the right versions. I am
The current ejb plugin can only compile EJB project into a normal JAR but it
is not some thing that can be deployed on WAS 7.0 as an EJB JAR. it does not
generates stubs and skeletons.
You probably just need to write all that code (and the configuration
etc) yourself and then just use the jar
The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the child poms do not
specify the version explicitly.
These are the projects that I am not getting correctly.
spring.batch.admin1.2.1.RELEASE/spring.batch.admin
Could it perhaps be caused by putting the dependency in the parent as a
dependency rather than a version in the dependency management section?
You might want to reread the Maven documentation or one of the books
about using a parent POM to manage versions.
It works fine if you do it right.
Yes. I just saw this note under 'Best Practices'
Maven uses the depth of a dependency in the tree when resolving conflicts
using a nearest-wins approach. Using the dependency *grouping technique
above pushes those dependencies one level down in the tree*. Keep this in
mind when choosing between
The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the
child poms do not specify the version explicitly.
Unless you are actively making a release, your version should almost
always have the -SNAPSHOT qualifier appended to it. So if you are
working on version 1.0, then your pom should show
On 24/04/2012 1:24 PM, Wayne Fay wrote:
The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the
child poms do not specify the version explicitly.
Unless you are actively making a release, your version should almost
always have the -SNAPSHOT qualifier appended to it. So if you are
working on
I tried, didn't work.
Below is my POM and build output. There is no maven-ear-plugin definition in
the parent POM.
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Hi everyone,
On Tue, Apr 24, 2012 at 12:51 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
If you have the same dependency in many modules and you want to ensure
that all developers are using the same version
This seems like an extremely common, if not ubiquitous, requirement to me.
Hi again,
I have seen people refer to a mystical depMgmt element but see no
mention of it in the Maven POM Reference.
Heh, I should do my research properly. Looks like people are just
abbreviating dependencyManagement which does exist in the POM reference:
dependencyManagement: is used by
Specifying versions in module level POMs opens the door to a module
having the wrong version during the build which can show up as a method
not found if the module was built with a version later than the one
provided at runtime.
I never said that I expect the module level POMs to have the
Hi
You have not configured your project to be an EAR project.
You need to add the following line to your POM, otherwise
maven-ear-plugin is never run, as can be seen in the log you provided.
packagingear/packaging
On 2012-04-24 19:58, hujirong wrote:
I tried, didn't work.
Below is my POM
Hello,
say I want to reuse some POM or system property as parameter in another
place in the POM but need it URL encoded. Does anyone know a Maven magic
to achieve this?
Programming a plugin to encode a given list of properties and provide them
under a different name seems no biggy, but I would
way is a good idea. I have seen people refer to a mystical depMgmt
element but see no mention of it in the Maven POM Reference. Anybody know
the details?
This is what you are looking for:
http://maven.apache.org/pom.html#Dependency_Management
And more documentation in the Sonatype book:
Wayne Fay wrote:
Specifying versions in module level POMs opens the door to a module
having the wrong version during the build which can show up as a method
not found if the module was built with a version later than the one
provided at runtime.
I never said that I expect the module level
Hi,
The Maven for PHP team proudly announces the release of Version 2.0.0 of
the PHP Maven plugin set (depending on maven 3). Details about the release
notes can be found in our google groups:
https://groups.google.com/forum/?fromgroups#!topic/maven-for-php/Z9sZ4xoWUoQ
The php plugins enables
My only use for versions specified by property is where the suite of
dependencies are all the same version. Properties is the only way right now
to handle that. Pom v5 should have something better when we get to it
shouldn't it, eh!
On Tuesday, 24 April 2012, Wayne Fay wrote:
way is a good
Hi
We use a internal Nexus repository. Now I want to set up an isolated test
environment. What's the best way to replicate the whole internal repository
into my Nexus?
Thanks
Jirong
--
View this message in context:
On 24/04/2012 8:59 PM, hujirong wrote:
Hi
We use a internal Nexus repository. Now I want to set up an isolated test
environment. What's the best way to replicate the whole internal repository
into my Nexus?
Why?
What are you trying to do with a separate repo?
Ron
Thanks
Jirong
--
View this
We use a internal Nexus repository. Now I want to set up an isolated test
environment. What's the best way to replicate the whole internal repository
into my Nexus?
I read this as ...Nexus... Nexus... Nexus...
Why are you asking this here? Please use the Nexus Users list for such queries.
Hi,
i am getting the following exception, while executing maven,
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] CustomerGrid
[INFO] Commons
[INFO] DTO
[INFO] BaseGridPlug
[INFO]
Hi, I'm facing a problem when including a subproject as a dependency in the
POM of my project. Code is like the following:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;...
modelVersion4.0.0/modelVersion
groupIdcom.test/groupId
The maven-compiler-plugin version is wrong.
maven-install-plugin:2.3.1 is ok
maven-compiler-plugin:jar:3.0.4 is wrong should be 2.3.2
Check out
http://maven.apache.org/plugins/index.html
Ron
On 24/04/2012 10:42 AM, Jeevan Reddy wrote:
Hi,
i am getting the following exception, while
This is more of a Hibernate problem than a Maven problem.
We use Hibernate and Spring and in the configuration file that includes
the HibernateSessionFactory, the reference to the hibernate
configuration file is specified as classpath:hibernate.cfg.xml since
the configuration file is in
34 matches
Mail list logo