Hey Luciano,
I'm glad you asked :-) I'm going to check with the EMF team on the ideal
solution mentioned below. I think that it's a much better request now that
there's a lot of people interested in it. Also I believe there's already
something in the EMF build for creating maven artifacts. Also, I think the
ALTERNATIVE SOLUTION would be the quickest to implement for now to get the RC
released.
IDEAL SOLUTION
I think the ideal solution would be to have the EMF team create emf artifacts
with each build, and publish those as well. I'll see what I can do to help
make this happen. I think the only thing left to do at that point is to create
a JIRA for the maven project to upload the dependencies to Ibiblio. I think
they get mirrored from there.
ALTERNATIVE SOLUTION
We just grab the standalone distribution, create maven repository artifacts out
of each jar, and create a JIRA for maven to upload the artifacts to ibiblio.
So I'll verify the process for the alternative solution first, and see whether
we can get that going real quick. Then I'll check with the EMF team to see
whether the ideal solution is a possibility.
Cheers,
- Ole
Luciano Resende wrote:
Hi Ole
This EMF dependency is the unique remaining issue in order to go
ahead with a DAS RC. Would you like to help us with this ?
SDO Guys, any other ideas/options ? I think this would be the same
issue for anyone trying to build SDO beta1 (or probably trunk as well)
from scratch today.
On 6/22/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
I would personally love to see the EMF dependencies committed to
Ibiblio. I need to get more familiar with the process though. I know
the ApacheDS artifacts get pushed to Ibiblio with each release.
Another option is to just make a local Tuscany repo for the EMF
dependencies. We could run a shell script (I think the EMF build has
such a script) that downloads the EMF jars, creates Maven repository
artifacts out of them, and then puts them in subversion or some other
http accessible location
Thoughts?
Luciano Resende wrote:
> Thanks Ole, got me further, but still missing some dependencies...
>
> Is there any chance we can make these dependencies available in one of
> our Apache maven repos ?
>
> On 6/22/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
>> I think this will have them:
>>
>> http://mirrors.cat.pdx.edu/eclipse/tools/emf/maven2/
>>
>> Cheers,
>> - Ole
>>
>>
>> Luciano Resende wrote:
>> > So, I saw Brian created a JIRA to increment EMF dependencies, but
any
>> > ideas of what could be done for our current dependencies ?
>> >
>> > On 6/22/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
>> >> Hi Luciano,
>> >>
>> >> I too can't find a 2.2 EMF artifacts maven repository at the
moment.
>> >> When Ole asked a similar question [1] on the EMF mailing list they
>> >> said they just don't offer EMF archives from a maven repo. I will
>> >> keep looking.
>> >>
>> >> Regards, Kelvin.
>> >>
>> >> On 22/06/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
>> >> > I'm trying to build a DAS release candidate, but I can't find a
>> maven
>> >> > repository that would have EMF 2.2.2 dependencies available.
The one
>> >> > being used today by SDO, looks like they don't have these
>> dependencies
>> >> > anymore.
>> >> >
>> >> > <repository>
>> >> > <id>indiana</id>
>> >> >
>> >> <url>http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/</url>
>> >> > <snapshots>
>> >> > <enabled>true</enabled>
>> >> > </snapshots>
>> >> > </repository>
>> >> >
>> >> > Ideas ? Other repos to try ?
>> >> >
>> >> > --
>> >> > Luciano Resende
>> >> > Apache Tuscany Committer
>> >> > http://people.apache.org/~lresende
>> >> > http://lresende.blogspot.com/
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >>
>> >>
---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
