For now, you can point to my unofficial repo http://ndeloof.free.fr/maven2
it contains sources and javadocs bundles for spring artifacts.
2007/1/15, Carlos Sanchez <[EMAIL PROTECTED]>:
http://opensource.atlassian.com/projects/spring/browse/SPR-1484
http://opensource.atlassian.com/projects/spring
David J. M. Karlsen wrote on Friday, January 12, 2007 12:14 PM:
> Hi!
>
> I've declared my parent pom as follows:
>
> artifactId>maven-javadoc-plugin
>
> 2.2-SNAPSHOT
>
>
>
> ${encoding.default}
>
> ${jdk.level}
>
>
and where did you put this? / and/or / ?
[snip]
- Jörg
-
I haven't used the assembly plugin but we have a similar scenario
addressed like this:
1) for Eclipse we have resources with hard-coded values. This works
well for running the app or tests from within IDE.
2) for packaging up using Maven, we use a combination of profiles and
filters to 'pa
Thanks Patrick,
That is how I started out configuring my POM - it made no difference as
to the error messages I got. The only difference is that with your POM I
need to explicitly specify the assembly goal on the command line.
mvn clean package
vs.
mvn clean package assembly:assembly
Thanks Mick,
I am having more success with the *fileSets*.
So it seems that my problem may be with how I have specified the
*moduleSets *which I have copied from a maven:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
The
For files like log4j and EasyConf, I don't want them buried in the jar
file as this makes it difficult to edit the files. I'd like them on
disk and for the jar file to include the directory on the classpath so
that the files can be located without worrying about file paths.
What I have been doin
I think the problem might be in your pom.xml... have you tried the standard
stuff?
[...]
[...]
[...]
maven-assembly-plugin
assembly.xml
[...]
On 1/14/07, Evan Toliopoulos <[EMAIL PROTECTED]> wrote:
+ Error
Try something like this:
This is my assembly descriptor:
tar
project-ear/target
*.ear
xdocs/**
${basedir}/src/main/resources/configs
Hi,
I noticed that if I set up filters inside the maven-war-plugin
configuration (snippet below) and run maven with -X flag the 'filters'
propety shows up as empty.
The resource understandably is not patched. However, setting up
under works and war plugin shows 'filters' populated
when ru
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.emagineinternational
admin-application
pom
1.0-SNAPSHOT
admin-application
http://maven.
http://opensource.atlassian.com/projects/spring/browse/SPR-1484
http://opensource.atlassian.com/projects/spring/browse/SPR-2704
They are aware, it's on their hands
On 1/14/07, Barrie Treloar <[EMAIL PROTECTED]> wrote:
I've submitted http://opensource.atlassian.com/projects/spring/browse/SPR-303
On 1/15/07, Steinar Bang <[EMAIL PROTECTED]> wrote:
> "Barrie Treloar" <[EMAIL PROTECTED]>:
> See http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin
> For steps on how to:
> * Build an internal repository containing the plugins from an Eclipse
> installation
> * Add the Eclipse RCP ar
Hi,
I don't have found this problem in the surefire plugin issues database.
Here is the problem i saw.
A. steps :
in a maven plugin test case, change the System properties to a new empty
Properties object
in the tested mojo, create another new Properties object with one value
store that last Pr
I've submitted http://opensource.atlassian.com/projects/spring/browse/SPR-3039
but if someone on the list knows who in the spring project to talk to
about making sure that source jars are always deployed to ibiblio that
would be great!
Thanks
-
Steinar Bang <[EMAIL PROTECTED]> writes:
> What does pom imply? In particular: why would
> one choose pom over jar?
>
Packgaging type is the single most important feature of a pom as it
defines the binding of mojos to the lifecycle used to builde that
project, which means what is done at what ti
> "Barrie Treloar" <[EMAIL PROTECTED]>:
> See http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin
> For steps on how to:
> * Build an internal repository containing the plugins from an Eclipse
> installation
> * Add the Eclipse RCP artifacts to your internal repository
A question: why i
Cheers but I don't want javadoc in my site, I want to manipulate it first,
if (for example) taking just the headings of each Java file and piece them
together into one xdoc file, not a whole bunch of HTML java docs. It just so
happens that xdoc would be a handy format to manipulate, if I have to
If you mean you're using the m2eclipse plugin, you should vote for
MNGECLIPSE-232. Reading the user-level settings.xml file is fixed
(MNGECLIPSE-29) but unreleased; you'll have to check the plugin out and
build it if you want to use that.
http://jira.codehaus.org/browse/MNGECLIPSE-232
Chris
> -
you don't need the embedder, check DefaultWagonManager
On 1/14/07, Rahamim, Zvi (Zvi) <[EMAIL PROTECTED]> wrote:
Hi,
I'm using the maven embedded and I want to retrieve a file from the
remote repository.
I want that it will be done in the same way a dependency/plug-in is
retrieved (with the same
There is already an enhancement and patch filed for this. You can
already include by types, if you want sources, you should be able to do
that already.
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 13, 2007 7:15 PM
To: Maven Users List
Subject: Re: U
Victor Okunev wrote:
>
> Can I create a dependency to a project with pom packaging? This would
> be convenient rather than creating separate dependencies on each
> module it contains. I tried but unsuccessfully, it seems that Maven is
> looking for a jar. Perhaps I am missing something?
>
> V
Good day to you, Gregory,
Actually, the plugin does not define the lifecycle. Rather, it's the
packaging type which defines the default goal bindings to the lifecycle
phases.
Regarding consolidating the functionality in order to minimize the effort
across pugins - if you're referring to implemen
Good day to you, Arnaud,
Pardon, I failed to read that part about the maven version :-)
Thanks for the correction.
- Franz
Arnaud HERITIER wrote:
>
> These settings are working only with maven 2.X.
> Not m1.x
>
> Arnaud
>
> On 1/13/07, franz see <[EMAIL PROTECTED]> wrote:
>>
>>
>> Good day
Hi,
On 1/11/07, Tobias Jenkner <[EMAIL PROTECTED]> wrote:
I do not understand the reason for this change?
why do I have to configure the resources directory on my own? the maven
approach is convention over configuration, isn't it?
or is it deprecated to use resources in this place? where should
Hi,
I'm using the maven embedded and I want to retrieve a file from the
remote repository.
I want that it will be done in the same way a dependency/plug-in is
retrieved (with the same protocol, with the same user/password, proxy
and so on...)
Can you tell me how can I do it?
Thanks!
--
Dennis,
I definitely agree. The sources plugin has been successfully used as
the mechanism for creating and deploying source jars to the the
repository. The reason that I brought it up was that any number of
artifacts can be deployed to a repository (
http://maven.apache.org/plugins/maven-assem
26 matches
Mail list logo