Hi All,
is there a task underway to update the Maven Ibiblio repository?
regards Malcolm Edgar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Henning,
thanks for that.
regards Malcolm
On 3/14/07, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
"Malcolm Edgar" <[EMAIL PROTECTED]> writes:
>Hi All,
>is there a task underway to update the Maven Ibiblio repository?
I don't know about ibiblio (this is maven-1, right?). Velocity
x27;t installed in the
maven2 repository yet. If someone knows what needs to happen to get that done,
i'd appreciate it if you could tell us. Also, please note that the POM
doesn't yet tell Maven2 how to do all that the Ant build can do.
> VelocityTools i
round.
> VelocityTools in Maven Repository
> -
>
> Key: VELTOOLS-60
> URL: https://issues.apache.org/jira/browse/VELTOOLS-60
> Project: Velocity Tools
> Issue Type: New Feature
> Components
Hi,
Not sure how it happened that for releases 1.0, 1.1, 1.2 you have POMs
and then for version 1.3 you don't but it wreaks havoc with anyone
trying to build with this in Maven.
It looks like someone did a manual release for 1.3 because the
metadata hasn't been updated correctly either. P
On 11/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Not sure how it happened that for releases 1.0, 1.1, 1.2 you have POMs
> and then for version 1.3 you don't but it wreaks havoc with anyone
> trying to build with this in Maven.
Sorry. I don't remember precisely (though a mailing list
Wrong Velocity 1.5 POM file in Maven repository
---
Key: VELOCITY-613
URL: https://issues.apache.org/jira/browse/VELOCITY-613
Project: Velocity
Issue Type: Bug
Affects Versions: 1.5
.org/maven2/org/apache/velocity/velocity/1.5/velocity-1.5.pom
?
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/jira/browse/VELOCITY-613
&g
urse. However, the wrong velocity is
referenced by maven-archetype-plugin, which is not my work. Of course, I could
as well file an issue in maven-archetype-plugin's issue tracker. For our
project where we use it, I've already created a workaround by posting new,
correct POM to our ma
as i don't recall
being the one to put that pom there. I also don't actually know the proper
way to fix this. If the maven folks say they need me to do this, please let me
know.
> Wrong Velocity 1.5 POM file in Maven repository
> ---
&g
uide-relocation.html,
http://maven.apache.org/pom.html#Relocation
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/jira/browse/VELOCITY-613
&g
whip a relocation pom and a set of
instructions for this? i'll carry them out, but i'd rather not spend much more
time on this than that.
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY
.5
>Reporter: Zdeněk Zikán
>
> Velocity's POM file in Maven repository has incorrect groupId:
> http://repo1.maven.org/maven2/velocity/velocity/1.5/velocity-1.5.pom
> It does not match the jar file
> Currently: org.apache.velocity
> Should be: velocity
--
This message i
daily (default), interval:X (where X is an integer in minutes) or never.)
Replacing all the existing POMs with a relocation POM should not be a problem,
since Maven will download again the POM if changed.
false
central
Maven Repository Switchboard
releasing a new pom there,
amongst numerous other instructions. The readme for the rsync repo says:
--
> cat README.txt
http://www.apache.org/dist/maven-repository
This is a Mav
d it to:
http://people.apache.org/~nbubna/velocity/engine/1.5/
in case we need to vote on it.
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/j
ocity jar directly it will be still fine.
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/jira/browse/VELOCITY-613
> Project: Vel
for catching that.
And it says no changes or deletions are allowed. So, i'm not sure i can even
change the POM after reading that. This might be something better taken up on
one of the Maven lists.
> Wrong Velocity 1.5 POM file in Mave
as update policy set to
"daily" so not sure why to enforce this restriction("After deploying, NO
CHANGES OR DELETIONS ARE ALLOWED from central repo or mirrors (only exception
the maven-metadata.xml files"). Maybe because you can override the settings in
your own POM - it
way to fix this, but honestly, i'd rather
just focus on getting 1.6 out the door.
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/
all relocation POMs
> Wrong Velocity 1.5 POM file in Maven repository
> ---
>
> Key: VELOCITY-613
> URL: https://issues.apache.org/jira/browse/VELOCITY-613
> Project: Velocity
> Iss
Velocity sources and javadocs missing in the maven repository
-
Key: VELOCITY-554
URL: https://issues.apache.org/jira/browse/VELOCITY-554
Project: Velocity
Issue Type: Bug
have an idea how to do
this, keeping in mind that Ant is used for releases?
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.
g Velocity 1.5 POM file in Maven repository
---
Key: VELOCITY-613
URL: https://issues.apache.org/jira/browse/VELOCITY-613
Project: Velocity
Issue Type: Bug
Affects Versions: 1.5
Reporter
y", is it Maven or Velocity?
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
&g
cern. Mine is that i can bend Ant to my will with
ease. Maven and i haven't gotten along that well historically. :)
Anyway, yes, the site is generated by Maven, which uses Velocity to do it. So,
it's both. But the site is not distributed in that form. Putting sources and
javadocs
sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
>
sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
>
sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
>
po/m2-ibiblio-rsync-repository/ so I will use SCP to
deploy the artifacts.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: h
b.sourceforge.net/tasks/tasks/propertyregex.html
Please let me know if the current changes are fine with you.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCI
ents: Build
>Affects Versions: 1.5
>Reporter: Aliaksandr Radzivanovich
> Attachments: VELOCITY-554_download.patch
>
>
> It is really annoying when popular projects like Apache Velocity do not
> provide their sources and javadocs to the Maven repository.
-
an. I've committed it.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Pr
7;t think there is any escape from this.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-5
worked as it should.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
>
ld
>Affects Versions: 1.5
>Reporter: Aliaksandr Radzivanovich
> Attachments: VELOCITY-554-2.patch, VELOCITY-554_download.patch
>
>
> It is really annoying when popular projects like Apache Velocity do not
> provide their sources and javadocs to the Maven r
http://repo.adrian.tarau.org
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
>
few tiny things and restored the
"pom" task, since i'm not ready to wholly rely on the new tasks for the 1.6
release.
> Velocity sources and javadocs missing in the maven repository
> -
>
>
aven-prepare
sould be
2. in maven-deploy-apache-repository
is not need it since is already called in
maven-prepare
> Velocity sources and javadocs missing in the maven repository
> -
>
> K
-ssh version in maven-prepare. The one in
maven-deploy-apache-repository was put there by the patch you sent. I'll
remove it. :)
> Velocity sources and javadocs missing in the maven repository
> -
>
>
fter splitting maven-deploy in two targets.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
&g
-m1-downloads and -m2-downloads, but this is actually not what I
meant. I meant bundling the maven-wagon tasks with Velocity to use them to
download the jars (and use things like mirrors etc.)
> Velocity sources and javadocs missing in the maven rep
ve access to this repository, but except
forcing a new repository location - - there are
the same.
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
>
en-prepare,release"
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> P
ions are for manual copying, so that's what i
did for 1.6.1. Wouldn't it work to just have ant name the file "sources"
instead of "src"?
> Velocity sources and javadocs missing in the maven repository
> ---
to change that. Or we could just create a task
which will copy all the maven artifacts in a separate folder(with one change :
src->sources).
> Velocity sources and javadocs missing in the maven repository
> -
>
>
dn't make the specific maven deploy tasks
depend on release, since release is a heavy target and would generally have
already be run. Also, the generic maven-deploy task depends on it already.
> Velocity sources and javadocs missing in the mave
1.6.2
> Velocity sources and javadocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
>
[
https://issues.apache.org/jira/browse/VELOCITY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Tarau reopened VELOCITY-554:
---
Velocity sources in main Maven
repository(http://repo1.maven.org/maven2/org/apache/velocity
ocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
> Issue Type: New Feature
>
opular projects like Apache Velocity do not
> provide their sources and javadocs to the Maven repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
ocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
> Issue Type: New Feature
>
ocs missing in the maven repository
> -
>
> Key: VELOCITY-554
> URL: https://issues.apache.org/jira/browse/VELOCITY-554
> Project: Velocity
> Issue Type: New Feature
>
9 PM:
-
Some maven related tasks didn't have depends="maven-prepare,release"
was (Author: adrian.tarau):
Some maven related tasks didn't had depends="maven-prepare,release"
> Velocity sources and jav
" or "maven-deploy-apache-repository"? I cannot
test this task, since I do not have access to this repository, but except
forcing a new repository location - - there are
the same.
> Velocity sources and javadocs missing in the maven repository
>
55 matches
Mail list logo
