Hello,
I have error below when running mvn site:deploy.
My maxs number of files seems to have appropriate values
cat /proc/sys/fs/file-nr
35840 20
What could be the problem?
[INFO]
[ERROR] BUILD ERROR
[INFO]
Hi,
For sample purposes, I've defined a custom lifecycle as follows:
project-archetypes-lifecycle
validate
org.apache.maven.plugins:maven-archetype-plugin:generate
Hi Markku,
Thanks a lot.
Previously my problem lie in that I missed the META-INF subdirectory under
"earSourceDirectory".
Best Regards,
Thunder
On Wed, Mar 17, 2010 at 12:37 AM, Markku Saarela wrote:
> You could use
> ${project.build.outputDirectory}
> and use normal build resources
>
>
>
>
yes.
you need to rethink your testing... perhaps the client module is
actually a test scoped dep of your war (assuming it is not a current
dep of your war) in which case you run the tests in the war module
Sent from my [rhymes with tryPod] ;-)
On 16 Mar 2010, at 17:59, Filippo De Luca
w
The Sonar Team is pleased to announce the release of Sonar 2.0. The main
feature of Sonar 2.0 consists in analysis of Design & Architecture and
object-oriented metrics. This new version enables to easily :
* remove cycles between packages by cutting undesired dependencies
* represent and n
Has anyone gotten the Maven release plugin to work on Windows with a CVS
SourceForge project. I've been working on this all day and have made some
progress but now I'm stuck. In my POM, I have my SCM defined as:
scm:cvs:ext:${cvs.userna...@ferris.cvs.sourceforge.net:/cvsroot/ferris:ferris-ass
Dan Tran writes:
>
>
>${basedir}/../../relative to your project
> directory
>
>
Well, that's better than nothing. I'm not thrilled about effectively
hard coding the location of the project this way.
> is there a reason why you want to do
Hi maven users,
I have a multimodule project with one war module and a jar module. The jar
module is a client for the war module.
The server pom contains:
org.mortbay.jetty
maven-jetty-plugin
10
/xxx-service
stop
8009
start-jetty
pre-integration-test
run-exploded
0
true
On 16 March 2010 14:37, Benson Margulies wrote:
> Just for fun, I think it's worth explaining the environment.
>
> We are relatively new adopters of Maven. Up until now, we've done
> maven releases only for external product releases. Thus, there are
> snapshot dependencies amongst our internal co
> I have an ejb project for which I need to generate an EJB jar (bean and
> interfaces) and a client jar (containing only the interfaces). I looked
> into using assemblies but that seems better suited for
I know its a huge hassle and very expensive to use Google, but try the
phrase "maven plugin
I followed this example:
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
So, I have all dependencies declared on the EAR and WARs now and the WARs
are "skinny"
But, there are some JARs that need to stay in the WARs (i.e. sitemesh)
because they won't work unless they are
> For me the above fix didn't help, it deployed ok, but the classes are not
> included into the final jars. I fixed the above problem as shown below. I
> guess the fix is only needed for WAS60, and probably only in certain cases.
You should submit a Jira for this so it will be included in a future
You could use
${project.build.outputDirectory} and
use normal build resources
src/main/resources
true
and put this weblogic file in subdirectory META-INF also you can define
additional resource directories there.. This way you can also filter
these files.
rgds,
Markku
On 16.3.2010 8:
> No tool is going to insulate you from bad human management practices.
> If 2 people are writing the same software module, they have to work to the
> same spec and coordinate themselves.
Ron nailed it. Communication is key!!
Wayne
I have an ejb project for which I need to generate an EJB jar (bean and
interfaces) and a client jar (containing only the interfaces). I looked
into using assemblies but that seems better suited for
completely different filesets/modules. Can anyone shed some light on the
right approach?
Thanks
Disable automatic snapshot checking (this is the default in M3) and
then you're fine. Nothing changes until you ask for updates.
On Tue, Mar 16, 2010 at 11:32 AM, Benson Margulies
wrote:
> On Tue, Mar 16, 2010 at 11:18 AM, Maven User wrote:
>> But then shouldn't you be building with what's avail
Benson Margulies wrote:
On Tue, Mar 16, 2010 at 11:18 AM, Maven User wrote:
But then shouldn't you be building with what's available, not a snapshot
created at some other time,
At time 0, I build everything. Components a, b, c, d. At time 1, a new
snapshot arrives for component a, and
On Tue, Mar 16, 2010 at 11:18 AM, Maven User wrote:
> But then shouldn't you be building with what's available, not a snapshot
> created at some other time,
At time 0, I build everything. Components a, b, c, d. At time 1, a new
snapshot arrives for component a, and unless i go back and run mvn
cl
But then shouldn't you be building with what's available, not a
snapshot created at some other time,
On Mar 16, 2010, at 10:37 AM, Benson Margulies
wrote:
Just for fun, I think it's worth explaining the environment.
We are relatively new adopters of Maven. Up until now, we've done
mave
Thiessen, Todd (Todd) wrote:
Interesting conversation. Let me add my two cents.
We do not yet have an aggregation POM that will build
everything and deploy the whole mess in a shot but that
should not be difficult to construct.
This statement is golden although I disagree with the "b
I removed that goal. Import your projects from M2Eclipse directly. There is no
interoperability between the maven-eclipse-plugin and M2Eclipse.
You have two choices:
1) Use the maven-eclipse-plugin and stock Eclipse
2) Use M2Eclipse
On Mar 16, 2010, at 6:37 AM, Dominique Jean-Prost wrote:
>
Just for fun, I think it's worth explaining the environment.
We are relatively new adopters of Maven. Up until now, we've done
maven releases only for external product releases. Thus, there are
snapshot dependencies amongst our internal components for months on
end. To make my original scenario a
Seems to be related to MECLIPSE-632
(http://www.mail-archive.com/users@maven.apache.org/msg106944.html)
I was rather surprised myself that is was removed without an explicit notice.
Seems like the m2eclipse guys will discontinue support for mvn
eclipse:m2eclipse in m2eclipse 1.0:
http://old.nabb
Hello,
After searching everywhere, I can't find why after upgrading to
maven-eclipse-plugin 2.8, I can not use eclipse:m2eclipse anymore.
Where can I find information about this ?
regards
INFO] Scanning for projects...
INFO]
--
Interesting conversation. Let me add my two cents.
> We do not yet have an aggregation POM that will build
> everything and deploy the whole mess in a shot but that
> should not be difficult to construct.
This statement is golden although I disagree with the "build everything" part.
Each arti
Is there a complete list of XML _attributes_ supported in the POM?
e.g.
[1]
[2]
[1]
http://www.sonatype.com/people/2007/06/how-to-merge-sub-items-from-parent-pom-to-child-pom-in-a-maven-plugin-configuration-2/
[2] http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
--
Vi
Phil Housley wrote:
On 16 March 2010 03:08, Ron Wheeler wrote:
Phil Housley wrote:
On 15 March 2010 22:29, Ron Wheeler
wrote:
Am I missing something?
There seem to be a lot of people who try to incorporate jar projects into
master projects and deploy with the "Big Bang" Theo
You could probably do a dependency:resolve and leverage the includes/
excludes - but that starts smelling hacky.
I'm in agreement with the earlier comment. If you're allowing any/all
devs to deploy, it can't be a free-for-all.
Why not let ci be the bottleneck (which implicitly has some degr
On Tue, Mar 16, 2010 at 4:18 AM, Benson Margulies wrote:
> If the answer is, 'always make a branch,' then that's the answer. It
> is not a popular answer with the developers I'm supporting. I wish
> there was some alternative involving controlling snapshot updates per
> g/a instead of per reposito
For me the above fix didn't help, it deployed ok, but the classes are not
included into the final jars. I fixed the above problem as shown below. I
guess the fix is only needed for WAS60, and probably only in certain cases.
At least it works for me now.
Arthur
public void execute() throw
I guess the issue is if you want to update some but not all of your
-SNAPSHOT dependencies. Maven does not provide filtering of update checking
On 16 March 2010 12:46, Maven User wrote:
> Google maven updatepolicy - you (as a user) can choose how often (or at
> all) you take versions from a repo
Google maven updatepolicy - you (as a user) can choose how often (or
at all) you take versions from a repository.
On Mar 16, 2010, at 8:18 AM, Benson Margulies
wrote:
Well, at least now we can see the disconnect. People don't want to
make a branch every time they are working on something
Well, at least now we can see the disconnect. People don't want to
make a branch every time they are working on something for more than a
day. (Default snapshot update is a day.) Making a branch is fairly
tiresome, especially given the difficulty of persuading release:branch
to work. The 'person' w
Hello,
Any progress made so far related to http://www.supose.org/issues/show/297 ?
Thanks
laurent
2010/3/4 Karl Heinz Marbaise :
>
> Hi Laurent,
>
>
> laurent.perez wrote:
>>
>> I'm sorry, I don't have much time right now to look at the plugin source
>> code :/
>>
> You don't need to apologize,
On 16 March 2010 03:08, Ron Wheeler wrote:
> Phil Housley wrote:
>>
>> On 15 March 2010 22:29, Ron Wheeler
>> wrote:
>>
>>>
>>> Am I missing something?
>>>
>>> There seem to be a lot of people who try to incorporate jar projects into
>>> master projects and deploy with the "Big Bang" Theory - Get
On 16 March 2010 04:25, Ron Wheeler wrote:
> Benson Margulies wrote:
>
>> I have this feeling that I'm missing something terribly obvious.
>>
>> 1: grab a tree and make some changes.
>> 2: mvn. Now you've got SNAPSHOT versions in your local repository
>> 3: someone else checks in a change and run
Best practice is one output per module. Is it not possible to make
multiple war outputs as different projects.
Subir
-Original Message-
From: Sudheer Gollapudi [mailto:sudheer.gollap...@gmail.com]
Sent: Tuesday, March 16, 2010 12:09 AM
To: users@maven.apache.org
Subject: Maven : Problem i
Hello
Iam working on a project where i have to convert the existing ANT based
project to a maven project.In this process iam trying to make multiple war
files out of a single source base.Iam using the maven build tag to do this
and here is a sample code that iam using in my pom.xml
38 matches
Mail list logo
