Hi,
I have a multi module web project. Four modules of the project are packaged
as jar and added as dependency to the fifth module, which is packaged as
war. When it is time to deploy the application i just run package on the war
project and my war is created with all the dependencies.
Now there
Actually I am using cobertura maven plug-in version 2.3 with maven version
2.1.
In my JUnits I have DB and EJB calls. During the build I use surefire maven
plugin property “forkMode=always” and with this property the unit test cases
pass properly. Otherwise Surefire plugin has problem running JU
On Fri, Apr 9, 2010 at 3:08 PM, sebb wrote:
> On 09/04/2010, Brian Fox wrote:
>> I said _after_ 1.6, but regardless it seems to be working normally:
>> http://repository.sonatype.org/index.html#nexus-search;quick~maven-core
>>
> Try the following:
>
> http://repository.sonatype.org/index.html#ne
On 09/04/2010, Brian Fox wrote:
> I said _after_ 1.6, but regardless it seems to be working normally:
> http://repository.sonatype.org/index.html#nexus-search;quick~maven-core
>
Try the following:
http://repository.sonatype.org/index.html#nexus-search;quick~maven
http://repository.sonatype.org/i
Most of the time when I look for something and get that problem I just the
advanced search with GAV serarch (awful name yes..) and find everything I
look for just fine.
> FWIW, Search rework is coming soon. Nexus 1.6.0 is coming out next
> week and then fixing the too many search results is next u
I said _after_ 1.6, but regardless it seems to be working normally:
http://repository.sonatype.org/index.html#nexus-search;quick~maven-core
On Fri, Apr 9, 2010 at 2:36 PM, Justin Edelson wrote:
> Actually, it looks like all search is borked now on r.s.o (which is
> running 1.6.0). Not the best si
Actually, it looks like all search is borked now on r.s.o (which is
running 1.6.0). Not the best sign guys :)
On 4/9/10 2:21 PM, Brian Fox wrote:
> FWIW, Search rework is coming soon. Nexus 1.6.0 is coming out next
> week and then fixing the too many search results is next up to slay.
> (And some
On 09/04/2010, Frederic Camblor wrote:
> +1 with Raphael
>
> I tried 1-2 searches this day ... and went back on mvnsearch and
> mvnrepository because of the "too many results" message :-(
Even gives the same message when searching for "sonatype" !
> Frédéric
>
>
> On Fri, Apr 9, 2010 at 8:00
FWIW, Search rework is coming soon. Nexus 1.6.0 is coming out next
week and then fixing the too many search results is next up to slay.
(And some other cool search enhancements)
On Fri, Apr 9, 2010 at 2:05 PM, Frederic Camblor wrote:
> +1 with Raphael
>
> I tried 1-2 searches this day ... and wen
rynam0,
I don't think the ${project.parent.basedir} variable is predefined. I tried
it, but maven doesn't recognize it.
Aymeric
rynam0 wrote:
>
> Have you tried using ${project.parent.basedir}?
>
> On Apr 9, 2010 3:31 AM, "Aymeric Alibert" wrote:
>
>
> Nick,
>
> The only solution I could
+1 with Raphael
I tried 1-2 searches this day ... and went back on mvnsearch and
mvnrepository because of the "too many results" message :-(
Frédéric
On Fri, Apr 9, 2010 at 8:00 PM, Raphael Ackermann <
raphael.ackerm...@gmail.com> wrote:
> I like the sonatype one as well. But if you search for
I like the sonatype one as well. But if you search for struts there,
the only thing you get is: Too many results, please refine the search.
Nexus could instead return newest result, possibly saying, click for
more or something. So unless you roughly know what version of struts
you want you won't ge
It does not seem to be very up to date. I prefer to use the sonatype nexus
instance that already catalogues most public repos..
http://repository.sonatype.org/index.html#welcome
> Yep, it's just the central repo for now. Haven't needed to use any
> others in my last few projects, but I could add
On Apr 9, 2010, at 2:54 AM, Andreas Sewe wrote:
> Kathryn Huxtable wrote:
>> My CPD HTML report is empty when I use maven-site-plugin 2.1. The XML report
>> is fine. The PMD report is fine.
>> If I use maven-site-plugin 2.0.1 I get my CPD report.
>> I don't know if this is a problem with PMD, Sit
It is a multi-module, but CoreDataSource is not the module being built.
We have an Ant script that runs the Maven builds for a bunch of
interconnected modules to test the end-to-end build process for the
project. CoreDataSource is one of the first modules built. Later,
another module uses that JA
> We've been building our application on Maven 2.1 for awhile just fine.
> We build it manually and with a continuous integration tool (Hudson)
Maven 2.1 had some issues. You really should move to 2.2.1 (or back to
2.0.11) before spending any more time trying to resolve this issue.
Wayne
---
Solved my issue, if your interested see StackOverFlow:
http://stackoverflow.com/questions/2606106/maven-deploydeploy-file-not-found-due-to-version-timestamp-appended-to-jar
Regards.
On 9 April 2010 09:36, James Clinton wrote:
> I'm have a problem using deploy:deploy-file with snapshots I'd like
Can you post the properties file you're referencing as well as the
resources section of the effective pom? This looks like a resource
filtering problem to me...
And when you say that "CoreDtaSource/core-datasource" is a separate
module in "the main build," do you mean that both
CoreDataSource/core
Chetan-
One thing I noticed in the blog entry is that you ran into trouble
parsing the POM file. This indicates that you are crawling central. Is
this true?
Justin
On 4/8/10 11:38 PM, Chetan Sarva wrote:
> Yep, it's just the central repo for now. Haven't needed to use any
> others in my last few
This would need a change to the accurev scm provider. The concept doesn't
map to maven's concept of an SCM but could be implemented with a system
property, or the provider could look for the existence of a an issues xml
file and provide that to the promote command as part of maven's "checkin"
pro
Have you tried using ${project.parent.basedir}?
On Apr 9, 2010 3:31 AM, "Aymeric Alibert" wrote:
Nick,
The only solution I could find is to create a 'filters' directory at the
project top level. The structure would be:
project/filters/filter-dev.properties
project/module1/src/main/filters/filt
I'm have a problem using deploy:deploy-file with snapshots I'd like some
advice on please.
I have 2 projects; 1) Ant based and 2) Maven based that consumes the jars of
the other project via Archiva.
I've added a target to the Ant project to deploy snapshots on every
successful build during our it
Kathryn Huxtable wrote:
My CPD HTML report is empty when I use maven-site-plugin 2.1. The XML report is
fine. The PMD report is fine.
If I use maven-site-plugin 2.0.1 I get my CPD report.
I don't know if this is a problem with PMD, Site, or Doxia, but I've filed
MPMD-119 to report it.
Has an
Nick,
The only solution I could find is to create a 'filters' directory at the
project top level. The structure would be:
project/filters/filter-dev.properties
project/module1/src/main/filters/filter-dev.proerties
and define the following in the POM:
${basedir}/../filters/fi
24 matches
Mail list logo
