cssparser-developers Mailing List for CSS Parser

Done.

I've uploaded it to SF and deployed it to our Maven repo, which I'll soon
request be sync'ed with the central repo.

Regards,

Daniel

On Thu, Mar 27, 2008 at 9:27 AM, Alan Krueger <al...@tr...> wrote:

> D&J Gredler wrote:
> > Does anyone mind if I cut a new release sometime in the next week?
> > Most of the bugs have been fixed and are now marked as such. All unit
> > tests are passing, and my "real world" usage with HtmlUnit seems to
> > indicate that things are OK.
> Sounds like a good idea to me.
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

D&J Gredler wrote:
> Does anyone mind if I cut a new release sometime in the next week? 
> Most of the bugs have been fixed and are now marked as such. All unit 
> tests are passing, and my "real world" usage with HtmlUnit seems to 
> indicate that things are OK.
Sounds like a good idea to me.

D&J Gredler schrieb:
> Does anyone mind if I cut a new release sometime in the next week?

+1 pro release
-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

Hi guys,

Does anyone mind if I cut a new release sometime in the next week? Most of
the bugs have been fixed and are now marked as such. All unit tests are
passing, and my "real world" usage with HtmlUnit seems to indicate that
things are OK.

Thoughts?

Daniel


-- 
Daniel Gredler
http://daniel.gredler.net/

[4th attempt to send this mail via list, 1st was 2008-03-25]

D&J Gredler schrieb:
> Anyways, I'll go ahead and set the min in the POM, but if anyone else has
> any comments, feel free to speak up.

Which Java 1.5 features are currently used or are planned to be used in 
cssparser in order to set the compatibility to version 1.5?

-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

[4th attempt to send this mail via list, 1st was 2008-03-24]

D&J Gredler schrieb:
> I want to close bug 1337724 (we're no longer compatible with JDK 1.2), which
> was opened 3 years ago. However, before doing so I'd like to clarify which
> JDK version the project requires. It seems to me that Java 5 should be the
> minimum, since that's when the DOM Level 3 APIs were first added to Java.
> What does everyone think?

Currently the project requires Java 1.4 (use of java.net.URI). I don't 
think we use DOM3 right now.

-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

Johannes Koch wrote:
> Alan Krueger schrieb:
>   
>> Testing non-subscriber posting to the cssparser-developers list.  Please
>> ignore.
>>     
> Not ignoring it for testing purposes...
Great, it looks like one of your attempts got through. =)

Alan Krueger schrieb:
> Testing non-subscriber posting to the cssparser-developers list.  Please
> ignore.

Not ignoring it for testing purposes...

-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

I refuse to ignore it!

;-)



On Wed, Mar 26, 2008 at 9:51 AM, Alan Krueger <th...@gm...> wrote:

> Testing non-subscriber posting to the cssparser-developers list.  Please
> ignore.
>
>

-- 
Daniel Gredler
http://daniel.gredler.net/

Testing non-subscriber posting to the cssparser-developers list.  Please
ignore.

Yeah, the project I'm currently working on is stuck at Java 5 due to our use
of OAS.

I think Java 5 is the new JDK 1.4 :-)

Anyways, I'll go ahead and set the min in the POM, but if anyone else has
any comments, feel free to speak up.

Regards,

Daniel

On Mon, Mar 24, 2008 at 12:30 PM, Alan Krueger <al...@tr...> wrote:

> D&J Gredler wrote:
> > I want to close bug 1337724 (we're no longer compatible with JDK 1.2),
> > which was opened 3 years ago. However, before doing so I'd like to
> > clarify which JDK version the project requires. It seems to me that
> > Java 5 should be the minimum, since that's when the DOM Level 3 APIs
> > were first added to Java. What does everyone think?
> I'm of two minds.
>
> At the Twin Cities Software Symposium in Minneapolis two weeks ago,
> almost a majority of the Java developers in attendance were still stuck
> on JDK 1.4 due to application server compatibility constraints.  This is
> often because of political issues, where a business stubbornly refuses
> to upgrade beyond some ancient version of Oracle AS, WebSphere, or
> whatever because it costs so freaking much, but won't consider migrating
> to something newer and cheaper.
>
> On the other hand, Sun's going to stop supporting 1.4 when 7.0 comes
> out, presumably sometime around this summer.
>
> I'm leaning toward 5.0 as the minimum, myself.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

D&J Gredler wrote:
> I want to close bug 1337724 (we're no longer compatible with JDK 1.2), 
> which was opened 3 years ago. However, before doing so I'd like to 
> clarify which JDK version the project requires. It seems to me that 
> Java 5 should be the minimum, since that's when the DOM Level 3 APIs 
> were first added to Java. What does everyone think?
I'm of two minds.

At the Twin Cities Software Symposium in Minneapolis two weeks ago, 
almost a majority of the Java developers in attendance were still stuck 
on JDK 1.4 due to application server compatibility constraints.  This is 
often because of political issues, where a business stubbornly refuses 
to upgrade beyond some ancient version of Oracle AS, WebSphere, or 
whatever because it costs so freaking much, but won't consider migrating 
to something newer and cheaper.

On the other hand, Sun's going to stop supporting 1.4 when 7.0 comes 
out, presumably sometime around this summer.

I'm leaning toward 5.0 as the minimum, myself.

Hi guys,

I want to close bug 1337724 (we're no longer compatible with JDK 1.2), which
was opened 3 years ago. However, before doing so I'd like to clarify which
JDK version the project requires. It seems to me that Java 5 should be the
minimum, since that's when the DOM Level 3 APIs were first added to Java.
What does everyone think?

Regards,

Daniel

-- 
Daniel Gredler
http://daniel.gredler.net/

Hi guys,

Not sure if you're subscribed to the commits ML, but FYI I've removed the
DOM and SAC classes, like we talked about. The DOM classes are in the JDK,
and I got the SAC JAR uploaded to the central repo (
http://repo1.maven.org/maven2/org/w3c/css/sac/1.3/); I've updated the POM so
that our project depends on this JAR.

Regards,

Daniel

-- 
Daniel Gredler
http://daniel.gredler.net/

Thanks again :-)



On Thu, Mar 20, 2008 at 5:40 PM, Alan Krueger <al...@tr...> wrote:

> D&J Gredler wrote:
> > I know I'm hounding you to death on this mailing list stuff, so let me
> > apologize in advance for another request ;-)
> >
> > I've never done it, but there's a way to send CVS change logs out on
> > the mailing list whenever someone changes something. This promotes
> > code review and makes it easier to discuss code changes.
> >
> > For example, I'm about to commit a fix to the CSS 2.1 grammar, but I'd
> > like to make sure other devs see it and can comment.
> >
> > Can you tinker around on the SF site and see if you can get this
> enabled?
> That should be enabled now.  Subscribe to the cssparser-cvscommits list
> if you want to see CVS log messages via email.
>
> https://lists.sourceforge.net/lists/listinfo/cssparser-cvscommits
>
> I've made this one "non-public" in SourceForge, which basically prevents
> a message archive.  Keeping an archive of CVS commit information in
> mailing list form seemed unnecessarily duplicative, but I've been
> mistaken before.  Let me know if this doesn't sound right.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Alan Krueger schrieb:
> Does anyone object to using Subversion for our source control?

I don't mind.
-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

D&J Gredler wrote:
> I know I'm hounding you to death on this mailing list stuff, so let me 
> apologize in advance for another request ;-)
>  
> I've never done it, but there's a way to send CVS change logs out on 
> the mailing list whenever someone changes something. This promotes 
> code review and makes it easier to discuss code changes.
>  
> For example, I'm about to commit a fix to the CSS 2.1 grammar, but I'd 
> like to make sure other devs see it and can comment.
>  
> Can you tinker around on the SF site and see if you can get this enabled?
That should be enabled now.  Subscribe to the cssparser-cvscommits list 
if you want to see CVS log messages via email.

https://lists.sourceforge.net/lists/listinfo/cssparser-cvscommits

I've made this one "non-public" in SourceForge, which basically prevents 
a message archive.  Keeping an archive of CVS commit information in 
mailing list form seemed unnecessarily duplicative, but I've been 
mistaken before.  Let me know if this doesn't sound right.

+1

I'd much rather work in SVN than in CVS.

On Thu, Mar 20, 2008 at 2:15 PM, Alan Krueger <al...@tr...> wrote:

> (The question was asked earlier, but in the middle of another message.
> I'll restate the question to ensure it doesn't get missed.)
>
> Does anyone object to using Subversion for our source control?  We can't
> use both SVN and CVS at the same time.  We would have to enable SVN,
> convert our existing CVS repository into SVN, then import that into SF's
> SVN repository.
>
> It takes a bit of work, but it should be easy to back out if something
> went wrong in the conversion process.  I'm in favor of Subversion
> myself, I've found it quite a bit easier to use than CVS and more
> powerful.
>
> Thanks,
> Alan
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

(The question was asked earlier, but in the middle of another message.  
I'll restate the question to ensure it doesn't get missed.)

Does anyone object to using Subversion for our source control?  We can't 
use both SVN and CVS at the same time.  We would have to enable SVN, 
convert our existing CVS repository into SVN, then import that into SF's 
SVN repository.

It takes a bit of work, but it should be easy to back out if something 
went wrong in the conversion process.  I'm in favor of Subversion 
myself, I've found it quite a bit easier to use than CVS and more powerful.

Thanks,
Alan

Hi Alan,

I know I'm hounding you to death on this mailing list stuff, so let me
apologize in advance for another request ;-)

I've never done it, but there's a way to send CVS change logs out on the
mailing list whenever someone changes something. This promotes code review
and makes it easier to discuss code changes.

For example, I'm about to commit a fix to the CSS 2.1 grammar, but I'd like
to make sure other devs see it and can comment.

Can you tinker around on the SF site and see if you can get this enabled?

Thanks again!

Daniel


-- 
Daniel Gredler
http://daniel.gredler.net/

Cool, thanks Alan :-)



On Thu, Mar 20, 2008 at 11:47 AM, Alan Krueger <al...@tr...> wrote:

> Alan Krueger wrote:
>
> D&J Gredler wrote:
>
>
> I think dev lists are usually public. Imagine, for example, that
> someone wants to become active in the project. The natural progression
> would be to read the mailing list archives, then subscribe and watch
> silently for a while, then maybe start becoming active on the
> mailing list, submit some patches, and then become a committer.
>
> Would you rather keep it private? If so, how come?
>
>
> Not really.  For some reason, I got it into my head that it should be.
>
> I plead a long week already at work.  =)
>
>
> It should be a public mailing list now.  New subscriptions also do not
> need approval.
>
> - Alan
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Alan Krueger wrote:
> D&J Gredler wrote:
>   
>> I think dev lists are usually public. Imagine, for example, that 
>> someone wants to become active in the project. The natural progression 
>> would be to read the mailing list archives, then subscribe and watch 
>> silently for a while, then maybe start becoming active on the 
>> mailing list, submit some patches, and then become a committer.
>>  
>> Would you rather keep it private? If so, how come?
>>     
> Not really.  For some reason, I got it into my head that it should be.
>
> I plead a long week already at work.  =)
>   
It should be a public mailing list now.  New subscriptions also do not 
need approval.

- Alan

OK, I think it's done.

If you don't have Maven yet, you can download it here:
http://maven.apache.org/download.html
Here's an intro to the standard M2 directory structure:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
The pom.xml file describes the project and drives the build, this page
documents the format: http://maven.apache.org/maven-model/maven.html
The standard build phases are described here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
The build uses the M2 JavaCC plugin to process the CSS grammars, see here
for more info: http://mojo.codehaus.org/javacc-maven-plugin/

Things you might want to try: "mvn install", "mvn test", "mvn clean", "mvn
eclipse:eclipse" (to generate an eclipse project that you can import).

Let me know what you think!

Regards,

Daniel



On Wed, Mar 19, 2008 at 8:20 PM, D&J Gredler <djg...@gm...> wrote:

> Hi guys,
>
> Nobody seemed to care much if I migrated to Maven, so I'm going to go
> ahead and give it a shot. I'll tag the repo first, so that we can roll back
> later if we don't like it. It shouldn't take very long, since the codebase
> is pretty small. I'll send an update / progress report later.
>
> Regards,
>
> Daniel
>
> --
> Daniel Gredler
> http://daniel.gredler.net/
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Hi guys,

Nobody seemed to care much if I migrated to Maven, so I'm going to go ahead
and give it a shot. I'll tag the repo first, so that we can roll back later
if we don't like it. It shouldn't take very long, since the codebase is
pretty small. I'll send an update / progress report later.

Regards,

Daniel

-- 
Daniel Gredler
http://daniel.gredler.net/

Hi Waldbaer!

I didn't realize that there was a SAC JAR published by the W3C. I'll try to
get it added to the central Maven repo.

As far as closing bugs that are already fixed, do you know which ones are
fixed?

Regards,

Daniel

On Wed, Mar 19, 2008 at 6:03 PM, Johannes Koch <ko...@w3...>
wrote:

> Hi Daniel
>
> D&J Gredler schrieb:
> > 3. The build currently excludes DOM and SAC interfaces from the
> generated
> > JAR.
> >     a. I think DOM exclusion makes sense, but I'd like to just delete
> these
> > interfaces from the repo.
> >     b. I think SAC exclusion doesn't make sense, and I'd like to include
> > them in the generated JAR.
>
> I don't understand why excluding DOM makes sense whereas excluding SAC
> doesn't. The SAC API can be found at
> <http://www.w3.org/2002/06/sacjava-1.3.zip> available from
> <http://www.w3.org/Style/CSS/SAC/>.
>
> > 5. Start fixing bugs!
>
> And start by formally closing already fixed issues   :-)
>
> Waldbaer
>
> --
> Johannes Koch
> In te domine speravi; non confundar in aeternum.
>                             (Te Deum, 4th cent.)
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/