In my parent Project the pom is:
com.mycompany.trademanager
all
pom
1.0-SNAPSHOT
common
junit
junit
4.3.1
test
In my child project the pom is:
com. mycompany.trademanager
all
1.0-SNAPSHOT
com.mycompany.trademanager
common
jar
1.0-SNAPSHOT
junit
j
On Sun, Oct 12, 2008 at 11:09 PM, Roger Ye <[EMAIL PROTECTED]> wrote:
> Without a pom, is there any mojo which I can use to download a certain
> artifact from maven repository server, into my local repo?
I don't see anything in a quick look around, but something like 'mvn
dependency:retrieve -Dgr
Hi,
Without a pom, is there any mojo which I can use to download a certain
artifact from maven repository server, into my local repo?
Maven local repository is excellent at managing only one copy of each
dependency, unfortunately I have a project which is not using maven, and I
want to put the de
You can see the line causing the NPE here:
http://maven.apache.org/plugins/maven-war-plugin/xref/org/apache/maven/plugin/war/packaging/WarProjectPackagingTask.html
I'd grab the source, add some debugging/tracing log entries, trace
down (and fix) the issue, and contribute it back via JIRA. Or open
http://www.sonatype.com/book/reference/optimizing.html
Ian Rowlands wrote:
I was wondering what is the best way to ensure (for build
reproduceability) that all plugins and the liked being used in the builds
have a specific version and not just picking up the latest version? Is
there a plugin
On Mon, Oct 13, 2008 at 6:05 AM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> You are specifying version 2.0.2.
>
> The website docs appear to be for 2.1-alpha-2 (note the Last Published
> etc near the top left corner). I would try that version instead, with
> this configuration, perhaps the NPE will go
Hello,
Does anyone know how to exclude a runtime dependency from the test
classpath? I am using RichFaces and TestNG. When I run my Seam TestNG
tests RichFaces tries to perform some operations which causes a test
to fail. I want RichFaces dependencies in my war file but I don't want
them
You are specifying version 2.0.2.
The website docs appear to be for 2.1-alpha-2 (note the Last Published
etc near the top left corner). I would try that version instead, with
this configuration, perhaps the NPE will go away.
Wayne
On Sun, Oct 12, 2008 at 7:07 PM, Alex Coles <[EMAIL PROTECTED]> w
I am encountering problems trying to exclude certain file types from
my WAR files. My WAR files are bloated, and becoming difficult to very
cumbersome to deploy to production servers.
Here's the two main types of files that should not be included in my WARs:
* Versioning Control Files (.git, .git
Thanks Dan, I'll check those
Oleg
Dan Tran wrote:
Oleg,
I switch my wagon url from dav to http, and it also fails due to
getFileList not implemented yet with your maven dist. this mean your
dist will break other plugins that requires fileFileList ( ie
wagon-maven-plugin and maven-stage-plugin
Oleg,
I switch my wagon url from dav to http, and it also fails due to
getFileList not implemented yet with your maven dist. this mean your
dist will break other plugins that requires fileFileList ( ie
wagon-maven-plugin and maven-stage-plugin )
-Dan
On Sun, Oct 12, 2008 at 1:51 PM, Oleg Gusako
On Thu, 09 Oct 2008 22:31:10 Michael McCallum wrote:
> theres a taste i probably missed something as this is just off the top of
> my head,
yes i did
don't use release poms if you expect version ranges to work... its just makes
a mess of everything and gets rid of your carefully crafted exclusion
This looks correct. If you run with -X it will show the mojo
configuration parameters and you can see if it is being passed in
correctly. If so, either the wD property does something different to
what you expect, or there is a bug in the plugin.
- Brett
2008/10/13 Mac-Systems <[EMAIL PROTECTED]>:
Unfortunately I don't think this is possible. What is the plugin in question?
- Brett
2008/10/12 Jiaqi Guo <[EMAIL PROTECTED]>:
> I ran into situation where a plugin configuration contains $ character. $$
> or \$ didn't seem to work. Any suggestions? Thanks.
> I'm using maven-2.0.9
>
>
> Regards
I don't quite understand your use case. Wouldn't it always run in
validate and block the others?
2008/10/12 Jon Strayer <[EMAIL PROTECTED]>:
> I have some executions attached to three phases (validate, process-resources
> & process-classes) that it would like to execute only once per build.
> What
As there is no reliable way for http client to get a list of files from
a generic dumb http server, I decided against implementing
getFileList(). And in the problem domain of accessing Maven
repositories, that is fine, because the problem of getting a content
list is solved on higher level - ab
In order to download file recursively and generically, i use
getFileList() to retreive a list of files available at the remote
server via a wagon url, after that, I iterate thru the list and
download file by file.
-D
On Sun, Oct 12, 2008 at 12:04 PM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
> Same
hmm, the wagon interface is generic, why do we want it to know any
thing about Maven repository like maven-metadata.xml?
-D
On Sun, Oct 12, 2008 at 12:04 PM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
> Same thing: instead of scraping html pages for the of of files - use
> maven-metadata.xml to get
Same thing: instead of scraping html pages for the of of files - use
maven-metadata.xml to get what files are available. The big issue, as I
mentioned, is lack of any metadata for classifiers, so you'll have to
try/fail for known classifiers: sources, javadoc, etc.
Now I am curious: what's the
Hello!
I recently found some really weird issue when doing the debug of the libraries
with attached sources in Eclipse. I used projects, which are being built by
Maven2. The problem is if any new dependency was added after the debug
configuration is created, then the source for the dependency is d
We we taking about the same thing here?
what getFileList() has any thing to do with metadata or maven-metadata.xml
-D
On Sun, Oct 12, 2008 at 9:16 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
> Try using the metadata? I count only on that in Mercury repository
> implementation. Plus I will p
Try using the metadata? I count only on that in Mercury repository
implementation. Plus I will provide a utility to create/correct
maven-metadata.xml files on the file system.
The only big problem is that classifiers are not covered anywhere, to
deal with them I had to extend the metadata mode
yup, getFileList is not there, but resourceExists is there.
I use both getFileList and resourceExists to figure out a list of
remote files recursively.
This way to plugin can base on that list and download files. However,
i can just docs
the work around to have user to use http wagon instead.
-
Oops - correction. resourceExists() I had to implement to pass ITs .
Dan Tran wrote:
Oleg, the mercury dav comes with 2.1-M2-SNAPSHOT has not implemented
Wagon.getFileList yet
[ERROR] FATAL ERROR
[INFO]
[INFO] The wagon yo
Correct, it did not. As well as resourceExists() - in those two I count
on metadata.xml to exist in the remote repo. And as it was not mandated
by ITs - I thought it's ok.
What breaks?
Oleg
Dan Tran wrote:
Oleg, the mercury dav comes with 2.1-M2-SNAPSHOT has not implemented
Wagon.getFileList
>> So what we need to do is put together a list of all the components that
went
>> into a build (so all the supporting maven plugins)
> Then I don't quite understand why the output of mvn help:effective-pom
> isn't what you need.
> Unless... you don't have the site plugin version locked down som
Hello,
anyone can tell me how to pass -DworkingDirectory in a POM for the
Changelog Plugin ? All my trys are ignored.
mvn -DworkingDirectory=C:\workspace\incubator\project scm:changelog
thanks,
Jens
-
To unsubscribe, e-m
the OP doesnot seem to be interested in doing things the right way, so
I was just suggesting a less bad way
Sent from my iPod
On 12 Oct 2008, at 09:34, Michael McCallum <[EMAIL PROTECTED]> wrote:
consider the in any situation where you want to change things based
on flags
its gets complica
consider the in any situation where you want to change things based on flags
its gets complicated.
why not just have a separate artifact that is very simple for each scenario...
there might be a little more setup but it means for a maven aware developer
they know that you have 5 projects theref
29 matches
Mail list logo
