[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gemini-dev] [gemini-jpa] - tycho build update...
|
Cristiano,
Yes, we will still store the project files since they are helpful to
people wanting to load the project into Eclipse.
We have been considering moving to git, but it isn't something that is
urgent for us.
Don't worry too much about the tests. Some of them will occasionally
fail because of ordering problems.
They need to be run in a test environment that facilitates controlling
the order more than it currently is.
-Mike
On 10/7/2011 7:29 PM, Cristiano Gavião wrote:
Hi Mike,
One question, using maven+tycho, lot of files will not be needed
anymore (.project, .classpath, .settings) they are generated by m2e
and is environment dependent. do you think is valid to mantain them at
SCM ?
Have you guys discussed the possibility to move to eclipse git
repository someday ?
I'm getting some problems with the svn env in my machine. The way I
found to get the code was using github and importing the data directly
from the svn...:
git://github.com/cvgaviao/Gemini-Dbaccess.git
git://github.com/cvgaviao/Gemini-JPA.git
I've used some free time today and I've changed the poms and some
manifests and I could run the build using tycho 0.13.0 and Juno
repository. I still getting some issues in tests, but ignoring the
tests builds ok. I will get a better look in weekend...
cheers
Cristiano
On 07/10/11 13:47, Mike Keith wrote:
Hi Cristiano,
Yes, referring to an existing P2 repo with DBAccess in it would be a
better solution that we are working towards. It's just that the
infrastructure was not in place when the JPA build was created. This
will all iterate very shortly towards that, though, since we are now
focusing on getting these things sorted out.
Thanks,
-Mike
On 10/7/2011 10:45 AM, Cristiano Gavião wrote:
Hi guys,
The project that I'm involved is using tycho 0.13.0 and Juno p2 for
it's building.
As we decided to do a prototype using gemini-jpa and need to create
a similar bundle for mysql, we start to update the dbaccess and
gemini-jpa to the new tycho version too.
I already finished Dbaccess with tycho 0.13.0 and using Juno p2. it
seems its running fine... at least no error message :)
I have a doubt related to %DBACCESS_URL% variable. I could see that
exists a prepare_build project that should be runned before to set
it...
Well, wouldn't be better to modify the gemini.dbaccess.updatesite to
produce a P2 repository (zipped locally or/and it can be deployed to
some http server) and point the target definitions of the
org.eclipse.gemini.jpa.targetdef project for this generated p2 repo
instead I had to run a prepare job?
cheers
Cristiano
_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev
