Nope. Same error, even after blowing away m2 and rerunning the basic
archetype to create a new app.
Chas.
Charles F. Munat wrote:
No on blowing away m2. I did switch to the blank archetype (which is
what I actually wanted) and it worked fine. But I can try again with the
basic and blowing
Can you please set scala.version dependency to 2.7.5 in pom.xml and re-
attempt.
You can do this by looking for scala.version/ element in the
pom.xml.
/Indrajit
On Aug 24, 11:06 am, Charles F. Munat c...@munat.com wrote:
Nope. Same error, even after blowing away m2 and rerunning the basic
Charles,
AFAIK I removed all dependencies to javax.servlet.* classes even from
archetypes. Are you using master? ... I did a full search and servlet
things are not being used. The archetype looks ok to me ... Am I
missing something?
Br's,
Marius
On Aug 24, 9:06 am, Charles F. Munat
Hi, Marius...
I don't know what you mean by Are you using master? What I did was use
the Maven archetype to create a basic JPA lift app. Then I changed
directory to the top directory and ran mvn compile. That's it. I got
the errors you see. I didn't do anything else.
I've tried blowing away
Charles,
Sorry for the false noise, setting lift-core dependency to
version1.1-M4/version instead of version1.1-SNAPSHOT/version
in web/pom.xml quite likely would help better.
/Indrajit
NB: I have had created a lift jpa project internally and played with
it for sometime. It took a while to
What I means is if you did a git pull from git master and ran mvn
clean:clean install. That inherently means version 1.1-SNAPSHOT
Br's,
marius
On Aug 24, 11:49 am, Charles F. Munat c...@munat.com wrote:
Hi, Marius...
I don't know what you mean by Are you using master? What I did was use
the
Tim,
Quite likely he is effectively on *latest* 1.1-SNAPSHOT as he used -
DarchetypeVersion=1.1-SNAPSHOT during archetype:create.
Would look forward to the archetype refactoring.
Meanwhile, I have created an issue summarizing the observations in
http://github.com/dpp/liftweb/issues/#issue/52.
Looking at the latest sources jar for the JPA basic archetype, it has the
proper changes:
http://hudson.scala-tools.org/job/Lift/1152/net.liftweb$lift-archetype-jpa-basic/
But I can confirm that something is not right with the JAR on there. I'm
going to try to do a local build and see if
Incidentally, I got that Maven command string straight out of the Lift book.
Chas.
Derek Chen-Becker wrote:
Looking at the latest sources jar for the JPA basic archetype, it has
the proper changes:
http://hudson.scala-tools.org/job/Lift/1152/net.liftweb$lift-archetype-jpa-basic/
But I
Yes, it compiles successfully when the lift-core dependency in the web
pom.xml file is set to version 1.1-M4.
Chas.
Indrajit Raychaudhuri wrote:
Charles,
Sorry for the false noise, setting lift-core dependency to
version1.1-M4/version instead of version1.1-SNAPSHOT/version
in
How would I know that? I presume that if I blew m2 away and then ran it,
I'd get the latest snapshot. Wouldn't I?
Chas.
Timothy Perrett wrote:
Chas,
Marius means are you using the *latest* 1.1-SNAPSHOT?
I have some works to do on the maven archetypes in the next couple of days
so I'll
I'm on a new laptop. I didn't do any git pulls of Lift stuff. I just
installed Scala with the IZ installer and then Maven, then I ran the
archetype command to create a basic JPA app and let it build the m2
repository on my machine. When that didn't work, I blew away m2 and
tried it again.
Chas,
The problem is quite likely with the archetype jar in the scala-tools
repo. Derek is probably looking into it.
Yes, your being confused about the master reference is
understandable :)
Good that it compiles through. For now, you can set the dependencies
to lift-core and lift-jpa to 1.1-M4
FYI, I did a local build and it's correct here, so something is going on in
Hudson land. I'm going to push a minor change to the pom for
lift-archetype-jpa-basic and see if that fixes it (remove the version for
the archetype plugin).
Derek
On Mon, Aug 24, 2009 at 12:23 PM, Indrajit Raychaudhuri
Thanks for all your help, Indrajit. I'm using the blank JPA app anyway,
so it didn't affect me, but I thought Derek, et al should know.
Especially since I was using the Maven command from his book...
Chas.
Indrajit Raychaudhuri wrote:
Chas,
The problem is quite likely with the archetype
OK, I think I've found an issue here. The sha1 checksum file for the
archetype was last updated on August 1st, and haven't been updated since
then. That's what your original error was, and it's why it's grabbing an
older version of the jar :(. Let me see if I can figure out why hudson won't
Ah, so the errors were connected after all. I was curious about the
checksum, but I didn't realize that would make it grab an earlier version.
Derek Chen-Becker wrote:
OK, I think I've found an issue here. The sha1 checksum file for the
archetype was last updated on August 1st, and haven't
Well. Bad news. I fixed the checksums only to find that somehow hudson is
still generating archetypes with old sources. I'm at a loss as to how this
is happening at this point...
Derek
On Mon, Aug 24, 2009 at 2:47 PM, Charles F. Munat c...@munat.com wrote:
Ah, so the errors were connected
OK, anyone with some maven-fu know what's going on here? It looks like the
build is fine, but the jar is being copied to a .archetype file instead of
.jar:
[INFO] Installing
Derek,
Im currently reorganizing the lift archetype codebase as we speak, so I’ll
look at it now...
Cheers, Tim
On 24/08/2009 23:03, Derek Chen-Becker dchenbec...@gmail.com wrote:
OK, anyone with some maven-fu know what's going on here? It looks like the
build is fine, but the jar is being
I think I may have found the issue. I had a packaging element in the pom
(none of the other archetypes do, as far as I can tell), so I've removed
that and I'm doing a local build to see if that fixes it.
Derek
2009/8/24 Timothy Perrett timo...@getintheloop.eu
Derek,
Im currently
OK, that seems to have been it. I just pushed a commit and I'll verify once
hudson builds it that it's working.
Derek
On Mon, Aug 24, 2009 at 4:36 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
I think I may have found the issue. I had a packaging element in the pom
(none of the other
There are several issues with the archetypes that I’ve found and I’ll be
checking in fixes soon... If you find this packaging issue please post what
it is and I’ll incorporate that with my commit shortly...
Cheers, Tim
On 24/08/2009 23:36, Derek Chen-Becker dchenbec...@gmail.com wrote:
I
Doh... I see you already committed it... (obviously didn’t see my other
post); I’ll attempt to do a merge with my local reorganized and fixed
archetypes.
Tim
On 24/08/2009 23:43, Derek Chen-Becker dchenbec...@gmail.com wrote:
OK, that seems to have been it. I just pushed a commit and I'll
Sorry about that. It's a one line commit, so hopefully Git will be able to
figure out a sane merge.
Derek
2009/8/24 Timothy Perrett timo...@getintheloop.eu
Doh... I see you already committed it... (obviously didn’t see my other
post); I’ll attempt to do a merge with my local reorganized and
I found this in the lift book and used it:
mvn archetype:generate \
-DarchetypeRepository=http://scala-tools.org/repo-snapshots \
-DarchetypeGroupId=net.liftweb \
-DarchetypeArtifactId=lift-archetype-jpa-basic \
-DarchetypeVersion=1.1-SNAPSHOT \
-DgroupId=com.foo.jpaweb \
-DartifactId=JPADemo \
It looks like this is still the older archive before HttpServletRequest →
HTTPRequest. The code in master has the change applied, so I'm not sure why
it's failing. The warnings are normal (I haven't figured out all of the
tricks with the velocity templating), but something isn't being pulled
No on blowing away m2. I did switch to the blank archetype (which is
what I actually wanted) and it worked fine. But I can try again with the
basic and blowing away m2.
Chas.
Derek Chen-Becker wrote:
It looks like this is still the older archive before HttpServletRequest
→ HTTPRequest. The
Fixed and committed. Sorry about that, I was out for the holiday weekend
here in the US.
Derek
On Sun, May 24, 2009 at 4:05 AM, Timothy Perrett timo...@getintheloop.euwrote:
Doh, this is due to the .gitignore file has exluded it (its not in the
git repo).
Derek has the sources for this, so
Doh, this is due to the .gitignore file has exluded it (its not in the
git repo).
Derek has the sources for this, so he'll need to add it specifically.
Cheers, Tim
On May 23, 11:41 pm, Charles F. Munat c...@munat.com wrote:
Another weird thing about the JPA blank archetype: there is an
30 matches
Mail list logo
