RE: Dependency plugin: tree, CLI substitution error

2015-05-31 Thread Dan Rollo
Hi Sander,

That was a big help! Thanks. And yes, surrounding the property in single quotes 
solved the problem. For example: -Dexcludes='${project.groupId}’ 

FWIW, the ${groupId} form did work (so I don’t think BASH was substituting the 
empty string because no such environment variable existed).

Mystery solved, not a maven issue, just my misuse of bash.

Dan


From: Sander Verhagen mailto:san...@sanderverhagen.net>>
Subject: RE: Dependency plugin: tree, CLI substitution error
Date: May 30, 2015 at 2:28:11 AM EDT
To: Maven Users List mailto:users@maven.apache.org>>


Hi,


Seems like your property is interpreted by BASH, which I don't think is what 
you want.

${BLAH} is a BASH variable, mostly equivalent to $BASH. I think what you meant 
is '${BLAH}', i.e. not substituted by BASH, giving Maven a chance to 
substitute. FYI, you wouldn't want "${BLAH}" either (with double quotes BASH 
will still substitute).

${BLAH.BLAH} is an invalid BASH variable, due to the period, hence its balking.

Your ${groupId} probably "works" in the sense that BASH doesn't complain. I 
don't think that it works in the sense that Maven substitutes it for the actual 
groupId. I don't think that it'll get the chance for that, because likely BASH 
already substitutes it for an empty string (assuming it doesn't know a groupId 
variable in your environment; not entirely sure on basis of the limited 
information given).

Hope this helps.



Sander Verhagen
[  san...@sanderverhagen.net   ]

Dependency plugin: tree, CLI substitution error

2015-05-29 Thread Dan Rollo
I’m using the maven-dependency-plugin to search for SNAPSHOT dependencies in a 
multi-module project. I am filtering out dependencies having the same groupId 
as the maven project. Here’s the command I use:

mvn dependency:tree -Dincludes=:::*-SNAPSHOT -Dexcludes=${project.groupId}

Unfortunately, this command produces the error below:

-bash: -Dexcludes=${project.groupId}: bad substitution


If I use the “old”, non-prefixed property name as shown below, the command 
works fine:

mvn dependency:tree -Dincludes=:::*-SNAPSHOT -Dexcludes=${groupId}


Is this a known issue? I would expect the "${project.groupId}” to work (and I 
think this is the “preferred” property syntax, no?)

The effective pom shows maven-dependency-plugin version 2.8.

More info: 
mvn -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
2014-12-14T12:29:23-05:00)
Maven home: /Users/bhamail/devtools/apache-maven-3.2.5
Java version: 1.8.0_40, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.3", arch: "x86_64", family: “mac"

Thanks!
Dan


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Missing parent link in site, was Re: Error resolving parent pom (descriptor?) with site plugin

2013-05-22 Thread Dan Rollo
Well, I never saw a response to this, and finally got tired of the 
missing 'parent' links in maven generated sites.


At some point, it appears the maven-site-plugin stopped using the parent 
projects URL, and instead looks for the parent projects 
distributionManagement -> site -> url to determine if the parent project 
is reachable during site generation.


So...to answer my own question: My workaround was to define a 
distMgt->site-url tag in the parent pom.


Due to the way m-s-p tries to inherit the parent value of this URL and 
then append it's own artifactId (which works if your parent is located 
above you - was more viable in a svn world, not so true in a git world 
anymore), I also have to re-define the distMgt->site->url again in each 
of my child poms to ensure the child site's value is correct.


Hope this might help anyone else who is wondering how to fix the message:
[WARNING] Unable to find a URL to the parent project. The parent menu 
will NOT be added.


(My original post was about a build problem, but the missing parent link 
was also annoying...)


Dan

On 12/12/2012 11:11 PM, Dan Rollo wrote:

Hi,

I'm seeing something I can't figure out, and wondering if this is a
known issue.

I have a multi-module maven project, which has as its parent a shared
corporate pom (in a totally different source bank location). I can build
this project successfully via "mvn package".

However, when I try to run the site goal, I get strange errors:

[INFO] Parent project loaded from repository: xxx:pom-parent:pom:1.0.1
...
[WARNING] Unable to find a URL to the parent project. The parent menu
will NOT be added.
Downloading:
http://xxx:8080/archiva/repository/cache-central/xxx/pom-parent/1.0.1/pom-parent-1.0.1.pom

mojoFailed org.apache.maven.plugins:maven-site-plugin:3.2(default-site)

and after that message, the build fails.


Just in case, I verified the parent poms site descriptor is available
both in our shared repo, and was downloaded to the local repo.


It as if the site plugin can't find the parent pom. Here's a another
error message:

Unable to read local module-POM
cause : SiteToolException: Unable to read local module-POM


Odder still, the "site" goal used to work fine. This problem just
started happening after I released a new version of the parent pom, and
updated the project to use the new released parent.

Thanks,
Dan



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



release plugin 2.3.2 adds to

2013-03-05 Thread Dan Rollo

This is not a problem report, but more an information request.
The  section in my poms never had a  section.
I just noticed the release plugin (2.3.2) is adding  to the  
section of poms during a release:



...
HEAD


The maven docs say this is the default value by convention (when not 
configured).


Also, in the tag created during the release process, the  is 
appropriately updated to the name of the newly created tag in the pom in 
that git tag.


Just wondering: when, and why did this behavior start?
I was surprised to see this new tag after doing a release, and would 
like to understand why it is needed. Is it a git/tag thing?


In case it matters, the scm is git.

Thanks!

Dan Rollo

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: 1.0.0-SNAPSHOT considered older than 1.0.0?

2012-12-20 Thread Dan Rollo

I created this bug report:

Maven Getting Started Guide should clarify SNAPSHOT qualifier of 
'version' element precedes release


http://jira.codehaus.org/browse/MNGSITE-167


Dan

On 12/20/2012 12:47 PM, users-digest-h...@maven.apache.org wrote:

Subject:
Re: 1.0.0-SNAPSHOT considered older than 1.0.0?
From:

Date:
12/20/2012 10:09 AM

To:
"Maven Users List" 


On Thu, 20 Dec 2012 15:08:26 +0100
Arnaud Héritier  wrote:


>I don't have the time to check the doc but if it's not in, this is a big
>error (don't hesitate to open an issue)
>A SNAPSHOT is the development version before producing the release.
>A SNAPSHOT is older than its release
>1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> ..

Thanks to all that replied.

The missing documentation I was referring to was:

   
http://maven.apache.org/guides/getting-started/index.html#How_do_I_make_my_first_Maven_project

Note:

   "We will discuss the use of snapshots and how they work further on in
   this guide"

The word "snapshots" doesn't appear again on the page.




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



re: Proper fix for "non-resolvable" dependency in build server

2012-12-19 Thread Dan Rollo

Hi David,

By any chance, does the maven goals you are executing include the 'site' 
goal?


I ask because I saw a similar problem where the build works fine as long 
as you do not try to build the site - mvn clean deploy worked, mvn clean 
deploy site-deploy failed.


I had the same case of a parent pom that was plubished in our lan repo
manager server. The parent pom was found, and downloaded to the CI 
servers local m2 repo fine, but some how the 'site' goal was not finding 
it (yet other build phases were fine).


To make matters more confusing, I found that if I manually ran "mvn
install" on the parent pom project on the CI server, then suddenly the
'site' goal was fine.

Please let me know if your problem is similar (and my apologies if it is 
not).


Thanks,
Dan

PS: I previously reported this in this post:
http://www.mail-archive.com/users@maven.apache.org/msg127878.html
but haven't seen any replies.


On 12/19/2012 10:24 AM, users-digest-h...@maven.apache.org wrote:
> Subject:
> Proper fix for "non-resolvable" dependency in build server
> From:
> "KARR, DAVID" 
> Date:
> 12/18/2012 10:26 PM
>
> To:
> Maven Users List 
>
>
> I have a project that is building fine on my laptop.  Today I started 
to set up the build for this on our Bamboo server.  Everything is 
checked in.  Both my laptop and the build server are using Maven 3.0.4.

>
> I have a top-level aggregator pom that specifies several modules, but 
this pom is not the parent of any module.  I do use parent poms, but 
those parents are in peer directories, and I have blank "relativePath" 
elements in all poms.

>
> In the Bamboo build of the top-level aggregator POM, I see several 
errors like this:

>
> [ERROR]   The project com.example.cde:java-project-parent:1.0.1 
(/volatile/bamboo/bamboo3.4.3_data/xml-data/build-dir/FOO-BUILD-JOB1/java-project-parent/pom.xml) 
has 1 error
> 18-Dec-2012 16:40:21 	[ERROR] Non-resolvable parent POM: Failure 
to find com.example.cde:project-parent:pom:1.0.0 
inhttp://hostname.net:8081/nexus/content/groups/stuff  was cached in the 
local repository, resolution will not be reattempted until the update 
interval of nexus has elapsed or updates are forced and 
'parent.relativePath' points at no local POM @ line 6, column 11 -> [Help 2]

>
> The "java-project-parent" is one of the poms in the parent hierarchy.
>
> I get that for some reason the "java-project-parent" artifact isn't 
in the local repository, but what exactly do I have to do to resolve 
this?  Do I have to run "mvn -U install" instead of "mvn install"?

>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Error resolving parent pom (descriptor?) with site plugin

2012-12-12 Thread Dan Rollo

Hi,

I'm seeing something I can't figure out, and wondering if this is a 
known issue.


I have a multi-module maven project, which has as its parent a shared 
corporate pom (in a totally different source bank location). I can build 
this project successfully via "mvn package".


However, when I try to run the site goal, I get strange errors:

[INFO] Parent project loaded from repository: xxx:pom-parent:pom:1.0.1
...
[WARNING] Unable to find a URL to the parent project. The parent menu 
will NOT be added.
Downloading: 
http://xxx:8080/archiva/repository/cache-central/xxx/pom-parent/1.0.1/pom-parent-1.0.1.pom

mojoFailed org.apache.maven.plugins:maven-site-plugin:3.2(default-site)

and after that message, the build fails.


Just in case, I verified the parent poms site descriptor is available 
both in our shared repo, and was downloaded to the local repo.



It as if the site plugin can't find the parent pom. Here's a another 
error message:


Unable to read local module-POM
cause : SiteToolException: Unable to read local module-POM


Odder still, the "site" goal used to work fine. This problem just 
started happening after I released a new version of the parent pom, and 
updated the project to use the new released parent.


Thanks,
Dan

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: How To Publish/Depend On Generated WSDL as Artifact?

2012-08-31 Thread Dan Rollo

Ping?

Maybe a different phrasing of the question would help:

How could I publish an artifact generated by a maven project, but also 
make sure that artifact did NOT include any dependencies? The desired 
result is: When some other project depends on this artifact, the project 
would not see any transitive dependencies.


For example:

myWSDL pom snippet:
...
com.mine
myWSDL
1.0-SNAPSHOT
...
  

  
org.codehaus.mojo
build-helper-maven-plugin
1.7

  
attach-artifacts
package

  attach-artifact


  

  target/generated/wsdl/mywsdl.wsdl
  wsdl

  

  

  

  


Some other project pom that uses the mywsdl file:

serviceClient
...


com.mine
myWSDL
wsdl
1.0-SNAPSHOT



How can I prevent 'serviceClient' project from seeing the transitive 
dependencies of 'myWSDL'?



I found other posts that mention things like:
'Maven Remote Resources Plugin' - 
http://www.mail-archive.com/users@maven.apache.org/msg112195.html


'Don't do it' - 
http://www.mail-archive.com/users@maven.apache.org/msg90783.html


We want non-maven projects to be able to use these WSDLs easily (eg: 
using maven ant tasks to pull in the WSDL), so even though a WSDL is a 
small artifact, we want to publish and version it as a standard artifact 
(with a custom "type").


Dan


On 08/28/2012 03:30 PM, Dan Rollo wrote:

Hi,

We have a maven project that produces both a .war file and a WSDL file.
The WSDL is auto-generated by the project. Right now we are publishing
the WSDL as an attachment (to the packaged 'war' file) with a custom
type="wsdl".

This allows us to use the WSDL artifact as a dependency in other
projects. The problem is when we use the "wsdl" dependency, it includes
all the dependencies of the project that generated the WSDL (eg: all the
deps of the 'war' project).

How can we publish/use a generated WSDL file, and avoid getting
dependencies that where used to generate the WSDL?

Thanks,
Dan Rollo



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



How To Publish/Depend On Generated WSDL as Artifact?

2012-08-28 Thread Dan Rollo

Hi,

We have a maven project that produces both a .war file and a WSDL file. 
The WSDL is auto-generated by the project. Right now we are publishing 
the WSDL as an attachment (to the packaged 'war' file) with a custom 
type="wsdl".


This allows us to use the WSDL artifact as a dependency in other 
projects. The problem is when we use the "wsdl" dependency, it includes 
all the dependencies of the project that generated the WSDL (eg: all the 
deps of the 'war' project).


How can we publish/use a generated WSDL file, and avoid getting 
dependencies that where used to generate the WSDL?


Thanks,
Dan Rollo

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: [MVN 3.0.4] Can't download project dependencies

2012-07-22 Thread Dan Rollo

Wow. That rawks!


Subject:
Re: [MVN 3.0.4] Can't download project dependencies
From:
Wayne Fay 
Date:
07/22/2012 12:01 AM
To:
Maven Users List 

> I worked with Linux, it's pretty good, but I prefer Windows (at least 
until

> Steam gets ported to Linux).

Good news for those of us who game on our PCs when not building apps
with Maven...
http://arstechnica.com/gaming/2012/07/valve-announces-ubuntu-port-of-steam-source-engine-and-left-4-dead-2/

Wayne


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



How to override "src/site" for site doc inputs?

2009-02-01 Thread Dan Rollo
Does anybody know of a good place to put some free-form documentation 
files in the maven project/pom.xml?


I know the default location appears to be "src/site", but I overrode the 
default source location when creating our pom.xml (to minimize changes) 
to be "src". Therefore, stuffing docs into the actual source code tree 
would be confusing (at best).


I couldn't see where to configure an override for the site input in a 
pom.xml.


Our project pom overrides are:

...

src
...
test
...


Thanks,
Dan

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: [m2] maven-checkstyle-plugin, v2.2 - includeTestSourceDirectory, xref links broken

2008-07-31 Thread Dan Rollo
Hi Dennis,

Done:

http://jira.codehaus.org/browse/MCHECKSTYLE-99

Title:  should use default test sources xref
output dir: ${project.reporting.outputDirectory}/xref-test


http://jira.codehaus.org/browse/MCHECKSTYLE-100

Title: Using  element truncates xref link to
"production" (non-test) classes

Thanks,
Dan


Subject:
Re: [m2] maven-checkstyle-plugin, v2.2 - includeTestSourceDirectory, xref
links broken
From:
Dennis Lundberg <[EMAIL PROTECTED]>
Date:
Thu, 31 Jul 2008 21:08:42 +0200
To:
Maven Users List 

Hi Dan

Please file these as 2 different issues for the Checkstyle Plugin:

http://jira.codehaus.org/browse/MCHECKSTYLE

Please include a complete pom.xml for each one, as it helps us to debug that
particular issue.

Dan Rollo wrote:
> I have configured the reporting section of my pom.xml to include the jxr
> report AND the checkstyle report (with the 
> element) as shown below:
>
> 
> 
> org.apache.maven.plugins
> maven-jxr-plugin
> 2.1
> 
>
> 
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.2
> 
> 
>
> config/jdbc4olap_checks.xml
>
> true
> 
> 
>
>
> I'm seeing the problems below:
>
> 1. The xref link to the Source pages in the checkstyle report page is
> broken. The source xref link for Unit Test Source files is not using the
> default value of the destDir for jxr test sources. From the jxr plugin
docs
> for jxr:test-jxr:
>
> destDir
>
> Folder where the Xref files will be copied to.
>
> * Type: java.lang.String
> * Required: No
> * Expression: ${project.reporting.outputDirectory}/xref-test
>
> I think the checkstyle plugin should:
> - assume the default dir for jxr:test-jxr
> - provide it's own additional override setting (similar to
xrefLocation,
> but for test sources). like: testXrefLocation.
>
> 2. When I include the  element, the source
xref
> link for "production" (non-test) classes has a mangled URL: the first
letter
> of the package is ommitted in the link:
>
file:///.../jdbc4olap/target/site/xref/org/jdbc4olap/xmla/XmlaProperties.html#10
>   
>
file:///.../jdbc4olap/target/site/xref/rg/jdbc4olap/xmla/XmlaProperties.html#10
>
> If I remove the  element, the xref links to
> production sources are fine.
>
> [BTW, there is a LICENSE.txt file at the root of my project (in case
anyone
> thought a missing default header file would affect this), and the
checkstyle
> report properly flags missing headers.]
>
> I searched for prior posts and jira issues about this, but found none. Is
> this a known issue? Should I file a jira? Any ideas on a workaround that
> would allow me to both  AND link to sources?
>
> Thanks,
> Dan
>


-- 
Dennis Lundberg


[m2] maven-checkstyle-plugin, v2.2 - includeTestSourceDirectory, xref links broken

2008-07-31 Thread Dan Rollo
I have configured the reporting section of my pom.xml to include the jxr
report AND the checkstyle report (with the 
element) as shown below:



org.apache.maven.plugins
maven-jxr-plugin
2.1




org.apache.maven.plugins
maven-checkstyle-plugin
2.2



config/jdbc4olap_checks.xml

true




I'm seeing the problems below:

1. The xref link to the Source pages in the checkstyle report page is
broken. The source xref link for Unit Test Source files is not using the
default value of the destDir for jxr test sources. From the jxr plugin docs
for jxr:test-jxr:

destDir

Folder where the Xref files will be copied to.

* Type: java.lang.String
* Required: No
* Expression: ${project.reporting.outputDirectory}/xref-test

I think the checkstyle plugin should:
- assume the default dir for jxr:test-jxr
- provide it's own additional override setting (similar to xrefLocation,
but for test sources). like: testXrefLocation.

2. When I include the  element, the source xref
link for "production" (non-test) classes has a mangled URL: the first letter
of the package is ommitted in the link:
file:///.../jdbc4olap/target/site/xref/org/jdbc4olap/xmla/XmlaProperties.html#10
  
file:///.../jdbc4olap/target/site/xref/rg/jdbc4olap/xmla/XmlaProperties.html#10

If I remove the  element, the xref links to
production sources are fine.

[BTW, there is a LICENSE.txt file at the root of my project (in case anyone
thought a missing default header file would affect this), and the checkstyle
report properly flags missing headers.]

I searched for prior posts and jira issues about this, but found none. Is
this a known issue? Should I file a jira? Any ideas on a workaround that
would allow me to both  AND link to sources?

Thanks,
Dan


Re: [m2] What triggers attempt to download from: http://cvs.apache.org/maven-snapshot-repository ?

2008-07-31 Thread Dan Rollo
Subject:
Re: [m2] What triggers attempt to download from:
http://cvs.apache.org/maven-snapshot-repository ?
Date:
Tue, 29 Jul 2008 20:38:41 -0700
To:
"Maven Users List"  

On Tue, Jul 29, 2008 at 2:36 PM, Dan Rollo
<[EMAIL PROTECTED]><[EMAIL PROTECTED]>wrote:

> > 1. Why are only SOME downloads hitting:
> > http://cvs.apache.org/maven-snapshot-repository/
> > when those same items exist in the normal central repo (and when I never

> > define the cvs.apache.org repo anywhere)?
> >
> > 2. Any idea how I can workaround this issue to avoid these long download

> > delays?

Unfortunately, your dependencies can introduce repositories to your build.

You can use mirrors in your settings.xml, specifically the
* section, to prevent Maven contacting extra
repos that show up.  See if this helps:
http://maven.apache.org/guides/mini/guide-mirror-settings.html

(It's not coming from the Apache parent pom-- the section that was
quoted is actually from distributionManagement, which controls where
Maven publishes to, not where it retrieves from.  I can tell from the
scp:// url.)

-- Wendy


Hi Wendy,

I was afraid you'd say that. The problem with any workaround involving
settings.xml is it doesn't help when someone downloads my project source and
builds with maven. Adding a README snippet that says: "To avoid long delays
in downloading, muck with your settings.xml like so..." is really ugly, and
breaks the wonderful "It just works" experience of building a new project
with maven.

I'm a little surprised to see this "implicit repo" introduced, as my
dependencies list is pretty small (copied below from my original post).


junit
junit
4.3.1
test



javax.xml.soap
saaj-api
1.3





com.sun.xml.messaging.saaj
saaj-impl
1.3
test







javax.activation
activation

true
1.1.1
runtime






Also, the only repo I explicitly include in my pom.xml is:





false

java.net
http://download.java.net/maven/1
legacy




In the interest of trying to make things better (instead of just whining), I
dug into the pom.xml in my local .m2 repo of each of these deps looking for
added repos. I found none. Also, there are no transitive dependencies for
the above deps.

Do you suspect the "implicit" repo:
http://cvs.apache.org/maven-snapshot-repository/
is being added by the java.net maven1 repo somehow?
And if so, any idea how to fix it (w/out mucking with settings.xml)?
I'd like to understand what is really going on here, and exactly what is
introducing this attempt to download from an unlisted snapshot repo.

Thanks,
Dan


Re: [m2] What triggers attempt to download from: http://cvs.apache.org/maven-snapshot-repository ?

2008-07-29 Thread Dan Rollo

Hi Martin,

Thanks for the reply, but I don't understand what you mean by "comment 
it out"? Where exactly would I comment it out?


I don't have any settings.xml, nor any reference to that repo in my 
pom.xml. If the repo is referenced in "one of the master poms", 
how/where can I comment that out?


Dan


Subject: Re: [m2] What triggers attempt to download from: 
http://cvs.apache.org/maven-snapshot-repository ?

To:
"Maven Users List" 

Dan
Its a repository located in one of the master poms e.g. apache-1.pom

   
 apache.snapshots
 Apache Development Snapshot Repository

scp://minotaur.apache.org/www/cvs.apache.org/maven-snapshot-repository
   

feel free to comment it out

Martin

- Original Message - From: "Dan Rollo" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, July 29, 2008 5:47 PM
Subject: Re: [m2] What triggers attempt to download from: 
http://cvs.apache.org/maven-snapshot-repository ?



> Forgot to mention: I'm using maven 2.0.9 :
>
> Maven version: 2.0.9
> Java version: 1.5.0_07
> OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Family: "unix"
>
>
> Dan Rollo wrote:
>> Apologies if I'm missing something obvious (and I did search the 
list archives without success).

>>
>> I have the following pom.xml defined for a project that depends on 
the activation.jar. I could only find that jar published on the maven 1 
repo on java.net.

>>
>> I deleted my local .m2 repo (to make sure I didn't botch the 
repo/dependency configs), and I ran: mvn clean package site
>> While maven is downloading all the needed plugins/deps, in the 
middle of the download, it starts trying to use: 
http://cvs.apache.org/maven-snapshot-repository/

>> for only some jars.
>> The download gets stuck on these for a long time (I assume until 
something times out).

>>
>> So I have a couple questions:
>>
>> 1. Why are only SOME downloads hitting: 
http://cvs.apache.org/maven-snapshot-repository/
>> when those same items exist in the normal central repo (and when I 
never define the cvs.apache.org repo anywhere)?

>>
>> 2. Any idea how I can workaround this issue to avoid these long 
download delays?

>>
>> I tried also re-defining the "central" repo in my pom before the 
jsvs.net.m1 repo (hoping that might always force checking of "central" 
before any other repo). Didn't seem to make any difference.

>>
>> Thanks,
>> Dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [m2] What triggers attempt to download from: http://cvs.apache.org/maven-snapshot-repository ?

2008-07-29 Thread Dan Rollo

Forgot to mention: I'm using maven 2.0.9 :

Maven version: 2.0.9
Java version: 1.5.0_07
OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Family: "unix"


Dan Rollo wrote:
Apologies if I'm missing something obvious (and I did search the list 
archives without success).


I have the following pom.xml defined for a project that depends on the 
activation.jar. I could only find that jar published on the maven 1 repo 
on java.net.


I deleted my local .m2 repo (to make sure I didn't botch the 
repo/dependency configs), and I ran: mvn clean package site
While maven is downloading all the needed plugins/deps, in the middle of 
the download, it starts trying to use: 
http://cvs.apache.org/maven-snapshot-repository/

for only some jars.
The download gets stuck on these for a long time (I assume until 
something times out).


So I have a couple questions:

1. Why are only SOME downloads hitting: 
http://cvs.apache.org/maven-snapshot-repository/
when those same items exist in the normal central repo (and when I never 
define the cvs.apache.org repo anywhere)?


2. Any idea how I can workaround this issue to avoid these long download 
delays?


I tried also re-defining the "central" repo in my pom before the 
jsvs.net.m1 repo (hoping that might always force checking of "central" 
before any other repo). Didn't seem to make any difference.


Thanks,
Dan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[m2] What triggers attempt to download from: http://cvs.apache.org/maven-snapshot-repository ?

2008-07-29 Thread Dan Rollo
Apologies if I'm missing something obvious (and I did search the list 
archives without success).


I have the following pom.xml defined for a project that depends on the 
activation.jar. I could only find that jar published on the maven 1 repo 
on java.net.


I deleted my local .m2 repo (to make sure I didn't botch the 
repo/dependency configs), and I ran: mvn clean package site
While maven is downloading all the needed plugins/deps, in the middle of 
the download, it starts trying to use: 
http://cvs.apache.org/maven-snapshot-repository/

for only some jars.
The download gets stuck on these for a long time (I assume until 
something times out).


So I have a couple questions:

1. Why are only SOME downloads hitting: 
http://cvs.apache.org/maven-snapshot-repository/
when those same items exist in the normal central repo (and when I never 
define the cvs.apache.org repo anywhere)?


2. Any idea how I can workaround this issue to avoid these long download 
delays?


I tried also re-defining the "central" repo in my pom before the 
jsvs.net.m1 repo (hoping that might always force checking of "central" 
before any other repo). Didn't seem to make any difference.


Thanks,
Dan


Pom.xml follows:

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

org.jdbc4olap
jdbc4olap
1.1-SNAPSHOT
jar

Jdbc4Olap
Jdbc4Olap is a JDBC Type 4 driver for OLAP 
datasources, which partially implements the JDBC 3.0
specification. It can communicate directly with most OLAP 
databases using the XMLA protocol : SAP® BW,

Microsoft Analysis Services®, Mondrian...

Furthermore, in order to support wider use, Jdbc4Olap includes 
a SQL-MDX converter and virtual relational map of

OLAP databases.

2008
http://www.jdbc4olap.org/



LGPL v2 license
http://www.gnu.org/licenses/old-licenses/library.txt

manual








fsiberchicot
Florian Siberchicot

fsiberchicot at users.sourceforge.net

admin
developer
        



bhamail
Dan Rollo
bhamail at users.sourceforge.net

developer

-5





scm:svn:https://jdbc4olap.svn.sourceforge.net/svnroot/jdbc4olap/trunk/jdbc4olap

scm:svn:https://jdbc4olap.svn.sourceforge.net/svnroot/jdbc4olap/trunk/jdbc4olap
http://jdbc4olap.svn.sourceforge.net/



src



${basedir}/jjtree

**/*.jjt




test






maven-compiler-plugin

1.5
1.5







org.codehaus.mojo
javacc-maven-plugin
2.4.1


jjtree-javacc

jjtree-javacc





1.5



jjtree








maven-source-plugin


attach-sources

jar







maven-javadoc-plugin


attach-javadocs

jar














org.codehaus.mojo
javacc-maven-plugin
2.4.1










false

java.net
http://download.java.net/maven/1
legacy







junit
junit
4.3.1
test



javax.xml.soap
saaj-api
1.3





com.sun.xml.messaging.saaj
saaj-impl
1.3
test